Concurrency Monitoring Usage API access cmu-api-usage-access
Access procedure overview api-access-procedure-overview
We have updated CMU reports access to be compatible with OAuth 2.0 Dynamic Client Registration Protocol. A custom OAuth 2.0 authorization server is deployed to address the needs of Concurrency Monitoring application.
In order for the Client applications to utilize the OAuth 2.0 authorization, the server must dynamically register to obtain specific information (client credentials) to be able to interact with it. As part of the registration process, the client must present a set of built-in metadata to the client registration endpoint.
This metadata is communicated as a software statement, which contains a “software_id” to allow our authorization server to correlate different instances of an application using the same software statement.
A software statement is a JSON Web Token (JWT) that asserts metadata values about the client software as a bundle. When presented to the authorization server as part of a client registration request, the software statement must be digitally signed or MACed using JSON Web Signature (JWS).
You can find a more detailed explanation on what software statements are and how they work in the official documentation [RFC7591].
Follow the steps in the sections below to gain access.
Access procedure steps access-procedure-steps
-
Have a registered application in Adobe Pass DCR server. For this step please contact our Support Team.
-
Get the software statement
-
Go to Adobe Pass TVE Dashboard
-
Select Programmer
-
Go to Registered Applications tab
-
Select application
-
Click download on the registered application row for which you want to get a software statement and save it as a file on your local machine
-
-
Obtain access token
-
Get client credentials by using the software statement obtained above and performing the bellow call. In this way a client_id - client_secret pair will be obtained, that can be used to get the access token.
This step should not be performed every time. It should be done again only when the credentials expire.
-
Get access token by using the bellow call. Use this access token to call any CMU API until the token will expire.
This step should be performed only if the last generated token expired.
-
-
Call CMU API - see related information bellow.
