-
Notifications
You must be signed in to change notification settings - Fork 24
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
okta_auth2.middleware.OktaMiddleware redirecting to login page #33
Comments
Getting the same issue |
I have the same issue as well. |
I ran into the same issue, it started to happen after a Django upgrade (Django versions 4.1 and lower were working fine Django versions 4.2 and higher stopped working) I created a PR that fixes this looping redirect issue and makes it so that session tokens are properly stored again: |
Hey sorry, I haven't been using Django now for a few years and this is super low on my priority list. I will try and find some time over the next week or two to catch up on it all. |
I'm having trouble with getting the Middleware to work.
I can successfully login via Okta and access the Django admin site, and other decorated views. However, this is while using the backend WITHOUT the okta_auth2.middleware.OktaMiddleware middleware. Once I enable okta_auth2.middleware.OktaMiddleware in MIDDLEWARE, all login attempts just redirect back to the login page.
I need some help determining where to look for issues. As I said, the auth works fine without the middleware in place, so I believe all configs are correct. Also okta auth is working 100% as users can login, groups are retrieved, etc.... For some reason, when enabling the middleware, it just doesn't work.
Without the middleware in place I need to override the admin login form to redirect to Okta, which I can do. However, I'd rather the middleware just do what it's supposed to.
Any tips would be greatly appreciated.
There are no errors anywhere, so not much to show right now.
The text was updated successfully, but these errors were encountered: