-
Notifications
You must be signed in to change notification settings - Fork 95
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
Logout doesn't work. It works only if we sign out of our gmail account (from the gmail website) #466
Comments
Did you enable "Log out from OpenID Provider" checkbox in plugin configuration? (disabled by default) |
Hello ! Yes the checkbox is checked on my end. |
It appears that Google does not provide |
So instead of going to any Jenkins page go to I'm pretty sure you are logged out, it's just when you go to any other page that requires authentication the login dance happens and you have already told Google this site is ok to login to, so it's virtually seamless. There may be an option you can set in the login URL (requires #443 that tells Google to choose an account or other so that the flow is not automatic) https://developers.google.com/identity/openid-connect/openid-connect#authenticationuriparameters see But if |
Jenkins and plugins versions report
Environment
What Operating System are you using (both controller, and any agents involved in the problem)?
Controller OS : Debian GNU/Linux 12 (bookworm)
Agent OS: Windows Server 2022
Reproduction steps
Expected Results
I should be asked to reconnect using my google account.
Actual Results
I am still logged in
Anything else?
This is the configuration that I have for the ioc plugin :
I noticed that the only way to log out is to sign out of my gmail account from gmail website, or by going here : https://mail.google.com/mail/?logout&hl=fr
The going back to jenkins, you will need to login again.
However signing out of gmail and signing out of jenkins should be two different things, and should not interfere between the apps behaviour.
Are you interested in contributing a fix?
No response
The text was updated successfully, but these errors were encountered: