Using Access Token Authorization with My Services API
The My Services dashboard and APIs are deprecated.
This topic explains how to set up and use access token authorization with the Oracle Cloud My Services API. Access token authorization allows a developer to access programmatic endpoints (APIs) to obtain some information (for example, entitlements, instances, or metering data) for your cloud account.
About Access Tokens
An access token contains the information required to allow a developer to access information on your cloud account. A developer presents the token when making API calls. The allowed actions and endpoints depend on the scopes (permissions) that you select when you generate the token. An access token is valid for about an hour.
A refresh token allows the developer to generate a new access token without having to contact an administrator. A refresh token is valid for about one year.
Process Overview
Setup steps for the Administrator:
- Create an Identity Cloud Service client application with the specific privileges you want to grant to developers.
- Generate an access token that contains the required privileges for the intended developer.
- Provide the access token and required information to the developer.
- Configure Identity Cloud Service for access token validation.
Steps for developer to use the token:
- Issue requests against My Services API endpoints. Include the access token for the authorization parameter.
- When the access token expires, refresh the access token without administrator intervention until the privilege is terminated.
Administrator Tasks to Set Up Token Validation
Perform the following tasks to enable developer access with an access token:
- Sign in to Identity Cloud Services as an Administrator and go to the administration console. See How to Access Oracle Identity Cloud Service if you need help signing in.
- Click the Applications tile. A list of the applications is displayed.
- Click + Add to create a new application.
- Click Confidential Application as the type of application.
- In the App Details section, enter a Name and Description. Avoid entering confidential information.
- Click Next.
-
In the Client section:
- Select Configure this application as a client now.
- Under Authorization, for Allowed Grant Types, select the following options:
- JWT Assertion
- Refresh Token
-
Under Token Issuance Policy, under Resources, click Add Scope.
-
In the Select Scope dialog, select CloudPortalResourceApp and click the arrow to select scopes for the resource.
-
Select the box next to each authorization that you might want to give the developers to whom you will provide an Access Token. (The permissions are assigned in another step.)
-
Click Add to close the dialog. Your selections are displayed.
-
Click Next.
- In the Resources section, accept the default and click Next.
- In the Web Tier Policy section, accept the default and click Next.
-
In the Authorization section, click Finish.
The Application Added notification displays the new Client ID and Client Secret for the application.
Important
Copy and store the Client ID and Client Secret in a safe place and then click Close. The Client ID and Client Secret are credentials that are specific to the application that you just created. You will need these credentials later. - To complete the creation process, click Activate at the top of the page.
-
Navigate to the IDCS application that you created in the preceding task and select the Details tab.
-
Click Generate Access Token.
-
On the Generate Token dialog, select Customized Scopes, then select Invokes Other APIs.
-
Select the scopes that you want to give to the developer who will receive this access token.
Note
Oracle recommends that you provide only the minimum required privileges. -
Select Include Refresh Token.
-
Click Download Token. Your browser will prompt you to download a token file (.tok). The token file contains an access token and a refresh token.
- Provide this file to the developer.
To call API endpoints, the developer needs:
-
A token file that you generated.
-
The Client ID and Client Secret for the IDCS application used to generate the token file. The Client ID and Secret are required for the developer to generate a new access token from the refresh token.
-
The endpoints for the APIs.
- End points related to the itas:myservices scopes are:
https://itra.oraclecloud.com/itas/<tenant-IDCS-ID>/myservices/api/v1 - End points related to the itas:metering scopes are:
https://itra.oraclecloud.com/metering/api/v1
- End points related to the itas:myservices scopes are:
Make sure that you send the above information in a secure way. If you think that this information has been compromised, see Revoking a Developer's Ability to Refresh Access Tokens.
To allow clients to access the tenant signing certificate without logging in to Oracle Identity Cloud Service:
- Sign in to the Oracle Identity Cloud Services admin console. See How to Access Oracle Identity Cloud Service if you need help signing in.
- Open the navigation menu. Under Settings select Default Settings.
- Set the Access Signing Certificate toggle button to on.
Using the Access Token
The token file has a .tok extension. The file contains the access token and the refresh token. The content looks like:
{"app_access_token":"eyJ4N...aabb...CpNwA","refresh_token":"AQID...9NCA="}To use the token with the My Services API:
- Open the token file.
-
Issue a request to a valid endpoint, inserting the access token for the
Authorizationparameter.For example:
curl -X GET https://itra.oraclecloud.com/itas/<tenant-IDCS-ID>/myservices/api/v1/serviceEntitlements -H 'Authorization: Bearer eyJ4N...aabb...CpNwA'
Requesting a New Access Token from a Refresh Token
An access token is valid for about one hour. When the token is no longer valid you will get a 401 response code and an Error Message ("errorMessage") value containing "Expired."
You can generate a new short-lived access token from the refresh token. You'll need the Client ID and Client Secret to generate the new token. You can only generate tokens with the same or lower access (scopes) as your original token.
Example using the curl command:
curl -i -H 'Authorization: Basic <base64Encoded clientid:secret>' -H 'Content-Type: application/x-www-form-urlencoded;charset=UTF-8' --request POST https://<tenant-IDCS-ID>/oauth2/v1/token -d 'grant_type=refresh_token&refresh_token=<refresh-token>'Using the sample token file from the previous section, the value for <refresh-token> would be AQID...9NCA=.
Sample response:
{ "access_token": "eyJraWQiO....2nqA", "token_type": "Bearer", "expires_in": 3600, "refresh_token": "AQIDBAUn…VkxNCB7djF9NCA=" }When a developer generates a new access token and refresh token, the previous refresh token becomes invalid.
Revoking a Developer's Ability to Refresh Access Tokens
If you need to revoke a developer's ability to refresh access tokens, you can either invalidate the existing refresh token by generating a new Client Secret for the token; or, you can temporarily revoke access by deactivating the application.
Taking either of these actions will terminate or suspend the ability of all developers using the current Client Secret or application. When generating tokens for multiple developers, consider creating more than one IDCS application to isolate developers from each other.
To terminate a developer's ability to refresh their access token
- Sign in to Identity Cloud Services as an Administrator and go to the administration console. See How to Access Oracle Identity Cloud Service if you need help signing in.
- Click the Applications tile. A list of the applications is displayed.
- Click the application used to generate the token to view its details.
- Click Configuration.
- Under General Information, next to Client Secret, click Regenerate to generate a new Client Secret.
To restore the ability for the developer to generate an access token from a refresh token, generate a new access token. Then provide the token along with the new Client Secret to the developer.
To temporarily suspend a developer's ability to refresh their access token
- Sign in to Identity Cloud Services as an Administrator and go to the administration console. See How to Access Oracle Identity Cloud Service if you need help signing in.
- Click the Applications tile. A list of the applications is displayed.
- Click the application used to generate the token to view its details.
- In the upper right corner of the page, click Deactivate.
- At the prompt, click Deactivate Application.
To re-enable developers to use the same tokens, click Activate.