-
Notifications
You must be signed in to change notification settings - Fork 81
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
Add support for Logout #7
Comments
Hi @jmelberg-okta, do you have any plans to add this feature? |
Hey @luksfarris! I'd love to be able to get this in before our |
Hi @jmelberg-okta , turns out it's harder than I expected 😅. I've created PR openid/AppAuth-iOS#191 for AppAuth, once it's merged I'll be able contribute here as well! |
Hi @jmelberg-okta , the pull request I've created for AppAuth is moving forward, but more work will be needed in the future. Meanwhile, I've created a pull request for you that does the logout on our side, here it is #30 . I don't expect you to merge it soon, but at least this is something for us to start working with. It works for my okta setup |
Hi @luksfarris, I extracted logoutFlow from your commit and modified it to call it directly from my app (not part of the SDK). I don't see any change in the logout behavior, the session still seems to be cached and the next login completes without any user interaction. Any ideas on what I'm missing? Thanks! |
Any progress on this? I'm working on an enterprise application where users check out and share company devices, and official support for a log-out flow would be wonderful! |
Thanks for your patience folks. We are waiting on AppAuth (the underlying library that we use) to add this functionality: Once this is merged and released, we will be in the position to update the Okta library. |
Closed via #103. We will be publishing a new version of this library soon with these changes, and the README has already been updated. If you need help with logout, let us know! |
Pending the release of OKTA-94106 terminate the user's session with Okta.
The text was updated successfully, but these errors were encountered: