How Does Siebel Application Use OAuth Tokens For OAuth Authorization During REST API
(Doc ID 2799477.1)
Last updated on AUGUST 18, 2021
Applies to:Siebel CRM - Version 17.0 [IP2017] and later
Information in this document applies to any platform.
in step 1, client application will make a call to OAuth server & Get token. In step 5, Siebel validates the access token with OAuth Server. At this step, does Siebel send every request to OAuth to validate the token even if it is the same token from previous request?
2. In the same flow diagram at step 4, The client server sends a request to the resource server. The request includes the access token in the HTTP header. Siebel Server looks for the USERID from the token to establish a Siebel Server session.
In this case at which level authorization happens. Is it at Application Interface(AI) level/at the Siebel server level?
3. What are the steps to be followed for OAuth to Access the Siebel REST API?
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document