Turned out, we had some unwanted spaces (%20) characters in authorization URL which was causing Adobe’s IdP implementation to return authorization code ignoring the scope we requested for, ending up in 403025 later. Getting rid of spaces in authorization URL fixed the issue for us.

Hi @Saurav_Raj  We have created product profile and assigned all permissions to it (reports suites, dimensions, metrics and rest). We also created oauth project from developer console Create New Project - >Add an API -> Add autentication Method. I think what I may be missing is linking product profi...

We are providing correct values for Global Company ID and IMS Org ID for headers x-proxy-global-company-id and  x-gw-ims-org-id respectively.What specific permission / entitlement setting I should be looking for in admin console?I have been give "Product administrator" access to my adobe account by ...

Hi David, We are facing exactly the same issue that you have reported here. Can you help us with what fixed the issue for you. Thanks,

We have successfully created OAuth 2.0 project type and were able to retrieve an OAuth2.0 access token using below approaches Using OAuth 2.0 Playground - Steps from https://adobeioruntime.net/api/v1/web/io-solutions/adobe-oauth-playground/oauth.htmlUsing OAuth 2.0 in POSTMAN - Steps from https://gi...