The Wayback Machine - https://web.archive.org/web/20201229075424/https://github.com/Widen/cloudfront-auth/issues/36
Skip to content

/ cloudfront-auth

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[Okta] 401 Nonce Verification Failed #36

Open
echoboomer opened this issue Jun 19, 2019 · 6 comments
Open

[Okta] 401 Nonce Verification Failed #36

echoboomer opened this issue Jun 19, 2019 · 6 comments

Comments

@echoboomer
Copy link

@echoboomer echoboomer commented Jun 19, 2019

I've set this up following the directions for Okta auth precisely and when I visit the CNAME address that points to this CloudFront distribution, I'm redirected to Okta for authentication. Once I authenticate, I receive an Error 401 Nonce Verification Failed message. Okta logs show that I authenticated successfully. Any thoughts on what is causing this?
@payton payton added the bug label Jul 20, 2019
@echoboomer
Copy link
Author

@echoboomer echoboomer commented Aug 5, 2019

Is there an update on a potential solution for this?
@echoboomer
Copy link
Author

@echoboomer echoboomer commented Sep 21, 2019

I switched to using Google auth and I'm getting the exact same issue.
@payton
Copy link
Collaborator

@payton payton commented Sep 22, 2019

@echoboomer Running through a fresh setup now to see if I can recreate the issue. Will update soon.
@echoboomer
Copy link
Author

@echoboomer echoboomer commented Sep 22, 2019 •
edited

@payton I will say that I tried this again yesterday using Google auth and it worked out fine as long as I used the CNAME in front of the Cloudfront distro instead of the URL of the distro itself for the redirect_uri field.
@payton
Copy link
Collaborator

@payton payton commented Sep 22, 2019

@echoboomer I see... Yes, that would cause a problem if using a CNAME. Two action items can be resolved from this issue:

  1. Explore alternative language for the nonce verification failed condition
  2. Update documentation to account for use of alternative domain names
@payton payton removed the bug label Sep 22, 2019
@plbenpeterson
Copy link

@plbenpeterson plbenpeterson commented Mar 10, 2020

@payton Hello - to resurrect this particular issue: I'm getting the same 401 Nonce verification failed error with Azure and have set the correct redirect_uri field as indicated above. For all I can tell, this should work but I get the error no matter what I try - any feedback on how I can troubleshoot this to get to the bottom of what the problem may be?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
3 participants
@payton @plbenpeterson @echoboomer
You can’t perform that action at this time.