Siebel OAuth REST Inbound Authentication Inbound Calls Creating Records Using Anon User Instead Of Actual User And Username Not Recognized In OAuth Token Generated (Doc ID 3030478.1)

Last updated on JUNE 25, 2024

Applies to:

Symptoms

Customer implements OAuth for REST Inbound and is making REST calls and creating accounts but the accounts are created using anonymous user.

The issue can be replicated using below steps:

1. Setup OAuth for REST Inbound using Doc ID: 2951362.2

2. Generate token and make sure token generation is successful

3. Use the token and test the Introspection URL to see if the response is received

4. Execute REST calls to create accounts and check if accounts are created properly for the user.

Expected Result:

Setting up OAuth on REST inbound services and while making inbound calls user specific token is passed as a bearer token in request, the records should be created using the actual user for which the token was generated.

Actual Result:

Creation of records is done by anonymous user instead of the user information for which token passed.

Changes

 N/A

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.