We are not able to generate Auth Code for Adobe Analytics

[AnkitDh1]

While trying to generate an authCode for Adobe Analytics, we are getting "login_required" error.

Below is the URL to generate authCode:

https://ims-na1.adobelogin.com/ims/authorize/v3
?
response_type=code&client_id=6a9*************redirect_uri=
https://us-west-2********************
&scope=openid,read_organizations,additional_info.projectedProductContext,additional_info.job_function&access_type=offline&prompt=consent

Below is the error message:

Has their been any recent updates in Adobe Analytics?

[FarazHusain]

A couple of things to check:

• Test the URL manually in a browser and ensure that it redirects to the login page without errors.
• Check the response returned after authorization in the browser's network logs.
• Verify the server receiving the redirect (AWS Glue) correctly processes the authCode.

One more thing that I found which you can try is to update the URL to include the prompt=login parameter along with prompt=consent to ensure the login screen always shows up, regardless of session state.

https://ims-na1.adobelogin.com/ims/authorize/v3
?response_type=code
&client_id=6a9*************
&redirect_uri=https://us-west-2.console.aws.amazon.com/gluestudio/oauth
&scope=openid,read_organizations,additional_info.projectedProductContext,additional_info.job_function
&access_type=offline
&prompt=login consent

If it is still an issue, please feel free to log a support ticket.

[AnkitDh1]

We have verified the URL manually and it is returning authCode correctly.

https://ims-na1.adobelogin.com/ims/authorize/v3?response_type=code&client_id=b4a****************&red...

Earlier it was working with 'prompt=consent', suddenly it has stopped working. 

So, what recent changes happed from Adobe side that we need 'prompt=login,consent'? 

[FarazHusain · Accepted solution]

Just to be clear, when I mentioned adding 'prompt=login,consent', it was just meant for testing purposes. I never mentioned that this is now required at Adobe's end. I'm not aware of any changes from Adobe's end. It could be something else as it is working manually. Had there been any changes, it would have returned the same results.

Hence, I would suggest logging a support ticket with all the required details. 

[Jennifer_Dungan]

Yeah, I would say Client Care is probably the best bet here... they should have access to more backend logs to drill right into the issue you are encountering... 

Good Luck!

[AnkitDh1]

How can we connect with Client Care?

[Jennifer_Dungan]

In Admin Console, there is a Support tab where you can create a ticket with Client Care.