2.2 Authentication

The Authentication Process involves the use of cURL Commands in a CLI Tool to generate the access token and invoke REST APIs. The Authentication Token is generated through the OAuth Client ID and Secret Credentials created in IAM/IDCS during Provisioning. The Authentication Token does not require that you log in to the AFCS Application to invoke the REST APIs from external applications.

Ensure that you have the appropriate log-in credentials for accessing the Oracle Transaction Filtering cloud service, and the appropriate role for creating, managing, and deleting service instances.

To get authentication, follow these steps:

  1. Log in to Admin Console. For more information, see Admin Console.
  2. Go to Component Details and click AUTH tab. The Client ID and Client Password details are displayed.
  3. Copy Client ID and Client password.
  4. Open Postman or relevant API tools. Select POST method and paste the URL: https://ip:port/oauth2/v1/token.

    Note:

    Replace ip:port with tenant URL or domain name.

  5. Click the Authorization tab. Go to the Type field and select Basic Auth from the drop-down list. The User name and Password fields are displayed.
  6. Enter the User Name and Password that you have copied in step-3.
  7. Go to the Body tab. Select request format as: x-www-form-urlencoded.
  8. Enter the KEY and Value fields as mentioned in the subsequent table:

    Table 2-1 Key and Value

    KEY VALUE
    grant_type client_credentials
    scope urn:opc:idm:__myscopes__
  9. Click the Header tab. The Header details are displayed.
  10. Enter the details explained in the subsequent table:

    Table 2-2 Key and Value

    KEY VALUE
    ofs_remote_user OFS_SRV_ACCT
    Content-Type application/json
    accept-language en-US,en-U
    authorization Bearer <Access_token>
    locale en-US
  11. Click Send. An Authorization token is generated in the Response body. For example, <eyJ4NXQjUzI1NiI6Ikk3cWxndm1Kal...>

    Note:

    This authentication key is valid for a stipulated time.

  12. Copy only the Authorization token details.