-
Notifications
You must be signed in to change notification settings - Fork 14
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
Cannot get past the 'Select Authentication System' screen, says 'Page Expired' #8
Comments
Can you provide a fiddler trace of the whole process? I kinda need to check what you are doing. Thanks. |
Thanks for the quick response. I actually got a little farther than my previous question by setting the IdpAdapterId = "ad..HTMLFormSimplePCV"; which showed the credentials screen but after adding Joe / 2Federate it redirects to the 'Page Expired' page... The below link is the redirect to get the authorization from ping...which appears to work..and is redirected to the credentials screen... I then supply Joe/2Federate the default user from the OAuth 2 Playground and then I am redirected to... https://localhost:9031/as/CnYAz/resume/as/authorization.ping which fails. I took your code from the Startup.Auth.cs from the Working Client solution, and updated the variables, and changed metadata=false, and added the endpoints because I could not get it working at all without that change from your code.. I also tried to increase the session timeout but that also did not help. Not sure what I am missing....any help would be great. I added my code below from my Startup.Auth.cs MVC project.
|
I recently set up the OAuth 2 Playground, and I am trying authenticate my MVC app with ping federate using your library. Similarly to the OAuth 2 Playground, I can get to the 'Select Authentication System' screen, I select HTMLFormSimplePCV and then the page redirects to 'Page Expired' I am never prompted for my credentials.
I updated my Startup.Auth.cs in my MVC app with your code, and client id, client secret, PingFederateUrl, and Endpoints.
The text was updated successfully, but these errors were encountered: