-
Notifications
You must be signed in to change notification settings - Fork 15
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
ExpressOIDC - 'post_logout_redirect_uri' not being passed correctly during Logout #12
Comments
@aarongranick-okta @shuowu-okta Can you help take a look? |
Any chance someone could look at this, sorry to be impatient but trying to work around it is killing my logout flow? @aarongranick-okta @shuowu-okta |
@CallSign-Filter While we are working on a fix for this issue, you can try okta-auth-js as a workaround. OIDC sample: https://github.com/okta/okta-auth-js/tree/master/samples/generated/express-web-with-oidc Internal Ref: OKTA-424753 |
@CallSign-Filter I figured out a workaround that doesn't require adding another dependency. I'm using the Express 4.x handle function in the app.get() that I use to clear my local session to call the oidc-middleware
Here's the source to where I got this answer from: https://stackoverflow.com/a/48820849/2644547 |
I'm submitting this issue for the package(s):
I'm submitting a:
Current behavior
When hitting the
/logout
endpoint, it is correctly routed through theoidc.router
and sends me to my Okta page to sign me out of Okta. But then I am getting a collision. My Sign-out redirect URI is correctly set here:But I am not catching my endpoint on my application (I am trying to clear some cookies and destroy the session)
You can see that I am sending the
post_logout_redirect_uri
parameter correctly here:But the call immediately after it, the
post_logout_redirect_uri
is changed to http://localhost:8080/Which leads me to this page here:
Expected behavior
The redirect URI is the same in my Okta settings, what is sent in the /login query, and my endpoint so it should call my endpoint on returning from signing out of Okta
Minimal reproduction of the problem with instructions
Environment
node -v
): 14.15.1The text was updated successfully, but these errors were encountered: