Intermittent Issue with Receiving Authorization Code in OIDC Login Flow #3878
Unanswered
ngocthanhqn95213
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi everyone,
I’m experiencing an intermittent issue with the OIDC login flow in my Android app using the AppAuth library. The problem occurs when the authorization code is supposed to be redirected back to the app client. Sometimes the app client receives the code, but other times it doesn’t, with a failure rate of about 1%.
Here’s an example of the login request sent by the client:
oauth2/auth?client_id=clientid&code_challenge=Q9hTYSQvtni6LqM-ObMjp67_QCaEbiaI5qlJAltck2E&code_challenge_method=S256&consent_verifier=77435023fc3842cc93a0a8133289af0a&nonce=IDWF8DDj9vgQORAqS9qV3g&redirect_uri=com.example.appauth%3A%2Flogin&response_type=code&scope=profile&state=I6-3NFm3qVuXKzcK5B9piw
However, when the authorization code is returned to the client, I decode the redirect URI appears as com.example.appauth:///login (with three slashes).
I’ve ensured that the redirect URI is correctly configured in both the app and the OIDC provider settings (com.example.appauth:/login). The issue seems to be related to the inconsistency in the number of slashes in the redirect URI.
Has anyone encountered a similar issue or have any suggestions on how to resolve this?
Thanks in advance for your help!
Beta Was this translation helpful? Give feedback.
All reactions