-
Notifications
You must be signed in to change notification settings - Fork 56
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
No Logout Configuration #32
Comments
Sorry, but the behaviour you describe is the intended one. When you log out, you close your session in your CKAN instance but not in your OAuth provider.
For this reason, if you click in log in again, you will be automatically log in, as you are already logged in your OAuth provider.
Br
Aitor
… El 28 ago 2019, a las 3:59, Sam Bradley ***@***.***> escribió:
There doesn't seem to be any way to configure the api call that gets made on logout so ckan isn't actually logging me out of my account i.e. when i press logout and then login I am not prompted to login again.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
In my (private) fork I solved this issue for keycloak. Since |
@aitormagan so in CKAN native there isn't a method that could handle this kind of issue? @pazepaze is that implementation visible on your repo? I don't use Keycloak unfortunately, perhaps could be useful have a look at it. Thanks for your attention. |
Sure, that's how I did it: in plugin.py
keycloak_openid is just the keycloak client instance from the python-keycloak library |
Hi @pazepaze , i just have a question. I tried to use your code and i have installed
Any ideas why this is happening? Thanks! |
There doesn't seem to be any way to configure the api call that gets made on logout so ckan isn't actually logging me out of my account i.e. when i press logout and then login I am not prompted to login again.
The text was updated successfully, but these errors were encountered: