To get started integrating the CORL portal with your GRC solution, create a custom API key.
The CORL portal uses a combination of a client secret (an API key) and a bearer token to allow access. The expectation is:
- Client generates API key(s) from the Client portal and stores the keys in their GRC application.
- Use the API key as an input to the authorization API which returns a JSON web token (jwt) token (token has a fixed period of validity).
- Use the jwt token in the header of API requests.
- Refresh the jwt token either (a) proactively before it expires or (b) when the system returns an error message.
Topics in this article include:
Create a new API Key
- Navigate to the Developer Portal. For more information, see GRC Integration Overview.
- Click API Key Manager.
- Click Create New API Key.
- Specify an API Key Name. Note: the name is not used for anything by the CORL system.
- Click Create.
- Click the Actions button.
- Copy the API Key value from the CORL portal to your application.
Change the API Key Name
- Navigate to the API Key Manager.
- Locate the API Key and click the Actions button.
- Change the API Key Name.
- Click Save API Key Details.
Delete the API Key
- Navigate to the API Key Manager.
- Click the Actions button.
- Click Deactivate API Key.
- The CORL Portal marks the key as Inactive. Tip: You can reactivate the key.