We are incorporating OAuth 2.0 Authentication Flow in our web client using instructions at https://www.adobe.io/developer-console/docs/guides/services/services-add-api-oauth/
We have been able to create Client Id and Client Secret using our developer account
Login using Client Id and Client Secret was successful, we got back access token as well, but the issue occurs when after login we try to hit any REST API in this case ‘get Project’ API. We get back 403025 error code (Profile is not valid)
So, we tried to create Client Id and Client Secret credentials inside a specific project now using account with ‘Role: Admin’
As we followed previously used steps to create credentials
We found out that in case of ‘Role:Admin’, the Adobe Analytics option is disabled so we were not able to create credentials as we did with ‘Role:Developer’.
Can some one please provide help on why we see the discrepancy between developer and admin account. We are not able to get the Oauth 2.0 integration working with any of the accounts .
Thanks,
Solved! Go to Solution.
Views
Replies
Total Likes
Hey @prateek_rajak
Can you check if In Admin Console you are a product admin or system admin.
Can you check In an Analytics product profile, you have access to web services as well as report suites and the dimensions/metrics you need access to.
Also, you need a separate Adobe.IO integration for each Experience Cloud organization.
Views
Replies
Total Likes
Can you verify that the user you authenticated is a member of a valid Analytics Product Profile?
Views
Replies
Total Likes
Hey @prateek_rajak
Can you check if In Admin Console you are a product admin or system admin.
Can you check In an Analytics product profile, you have access to web services as well as report suites and the dimensions/metrics you need access to.
Also, you need a separate Adobe.IO integration for each Experience Cloud organization.
Views
Replies
Total Likes
Views
Likes
Replies