OAuth2 Client Credentials Flow
OAuth 2.0 Protocol
The following illustration is the depiction of the ForeSee<sup® OAuth 2.0 Client Credentials Grant Flow:


How Authentication Works
- Contact ForeSee to register as a new API client. A successful registration returns the client credentials (client_id, client_secret) tuple.
- Client uses credentials to log into the Authorization Server.
To illustrate this process, the following call is first made: /token?grant_type=client_credentials&scope=. This is an HTTPS POST and contains an Authorization Header that has the following format: Basic <Base 64 encoded value formed from client_id:client_secret>.
Example:
Basic WEpLbmhrVEtQTnRLdlVNaEs1Vk5kM01XSTlWSTBRem46OEF2VFllN1JYczL0cE1KOW1EVzg=
Example using Postman:


A successful authentication returns an Access Token. Example:
{
"access_token": "80965804-63cc-45a8-8ce3-983da1d6ef64",
"token_type": "bearer",
"expires_in": 899,
"scope": "r_basic"
}
By default, the token is valid for 15 minutes. A longer expiration time can be requested from Verint Support if needed.
- Input the Access Token into the Authorization Header as the Bearer Token to make calls into your data, which is stored in the Resource Server.
Example using Postman:


Updated almost 2 years ago