Thank you so much for your response.
To resolve the issue, I added the main folder name "OAuthSimulation" to the SOCP configuration. After this change, the 403 Forbidden error was resolved."
API Service Path: OAuthSimulation.services:apiCallWithToken
Before adding Main folder Name: API is returning 403 Forbidden error.
After Adding Main folder Name: API Returning 200 Ok
Scope Configuration:
API Response:
Thanks,
Abdulla Pulicherla
Original Message:
Sent: Fri May 30, 2025 04:43 AM
From: Nugroho Hermanto
Subject: OAuth implementation in ESB (Enterprise Service Bus) without using an API Gateway.
Hi Abdulla, I have also experienced the same issue. For the time being, you can probably configure the oauth scope by adding ".*" to the "Folders and services" column. This does mean that the Oauth scope covers all existing objects, but this can make testing continue until we find the right solution or someone else shows a safer solution.
Hope this helps.
------------------------------
Nugroho Hermanto
Original Message:
Sent: Wed May 28, 2025 03:53 AM
From: Abdulla Pulicherla
Subject: OAuth implementation in ESB (Enterprise Service Bus) without using an API Gateway.
I have successfully configured the Client, Scope, and am able to generate the Access Token. However, when I pass the access token to invoke a Business API (apiCallWithToken), I receive the following error:
error_description=[ISS.0010.8046] Integration Server rejected the request to access this resource. The access token's scope is insufficient to access the resource.
Please note that I have already added my REST resource into the defined scope.
ScopeAssociateToClients
ACL Mapping to services:
ACL mapping for API Resource
ACL mapping to Actual API:
Looking forward to your guidance on resolving this issue.
------------------------------
Abdulla Pulicherla
------------------------------