OAuthAuthenticationHandler extractCredentials: fallback to we can't handle this | Community
Skip to main content
maksyms28136728
maksyms28136728
October 27, 2020
Solved

OAuthAuthenticationHandler extractCredentials: fallback to we can't handle this

  • October 27, 2020
  • 2 replies
  • 3186 views

Hi,

 

I've implemented a custom OAuth Provider and API. 

So currently AEM redirects to OAuth form, and after successful login user is redirected back to AEM with

authorization_code as a parameter 
http://localhost:4503/content/site/en/welcome.html?code=W8kJTZV9syQJ8JOuPWMTCeP_x2C190y-9CmWehunGpM&state=s5vraqvk34thmc5koifac1kbla

The problem is that OAuthAuthenticationHandler doesn't see authorization_code as a request param:

com.adobe.granite.auth.oauth.impl.OAuthAuthenticationHandler extractCredentials: fallback to we can't handle this

 as a result, there is the following error in logs:

com.adobe.granite.auth.oauth.impl.helper.OauthTokenManager token not found in request attribute or cookie for:customOAuth

 

Why code param is not visible for OAuthAuthenticationHandler? How could it be debugged to understand the root cause of this issue?

 

Thank you in advance!

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by AlbinIs1

Are you using JsonTokenExtractor?

 

Login form should redirect to url that ends with "/callback/j_security_check"

that triggers AEM code to make an additional call to OAuth service to get Access Token

 

Refer to the below URL for more detail -

https://github.com/techforum-repo/bundles/blob/master/google-oauth-provider/src/main/java/com/core/oauth/google/GoogleOAuth2Api.java

https://techforum.medium.com/social-login-with-google-oauth2-adobe-experience-manager-aem-ff33b5c4f349?source=your_stories_page-------------------------------------

Regards

Albin I

www.albinsblog.com

 

2 replies

A
Community Advisor
AlbinIs1Community AdvisorAccepted solution
Community Advisor
October 28, 2020

Are you using JsonTokenExtractor?

 

Login form should redirect to url that ends with "/callback/j_security_check"

that triggers AEM code to make an additional call to OAuth service to get Access Token

 

Refer to the below URL for more detail -

https://github.com/techforum-repo/bundles/blob/master/google-oauth-provider/src/main/java/com/core/oauth/google/GoogleOAuth2Api.java

https://techforum.medium.com/social-login-with-google-oauth2-adobe-experience-manager-aem-ff33b5c4f349?source=your_stories_page-------------------------------------

Regards

Albin I

www.albinsblog.com

 

    maksyms28136728
    maksyms28136728Author
    November 2, 2020

    Hi Albin,

    Thanks for response!

    I am not using JsonTokenExtractor. I followed same link that you provided.

    From the logs i see that AEM tries to find authorization_code in request before request comes back from OAuth login page.

    so log looks like this:

    com.adobe.granite.auth.oauth.impl.helper.OauthTokenManager token not found in request attribute or cookie for:custom_config
    GET /content/redirect/path.html?code=CodeFromTheOAuth&state=some_state HTTP/1.1

     

    A
    Adobe Employee
    AnujSPatelAdobe Employee
    Adobe Employee
    August 24, 2023

    Hi @maksyms28136728 

    I am facing exactly same error where the call to token endpoint is not made after redirect to callback url with auth code as parameter. Were you able to resolve this issue?

    Any help is highly appreciated, thanks. 

    maksyms28136728
    maksyms28136728Author
    November 3, 2020

    I found the issue.

    Login form should redirect to url that ends with "/callback/j_security_check"

    that triggers AEM code to make an additional call to OAuth service to get Access Token

     

      Terms & ConditionsAccessibility statement

      Loading footer...