Kohsuke Kawaguchi resolved Bug JENKINS-16350 as Won't Fix

I don't see how to fix this.

As kylecordes wrote, what's really happening is:

  • Jenkins logs you out, redirects you back to the Jenkins page you were in.
  • Jenkins sees a new you, now anoanymous. It decides to authenticate you.
  • Jenkins sends you to OpenID server
  • OpenID server is configured to automatically log you in (aka "remember this website")
  • Jenkins logs you right back in.

This happens if (1) you use OpenID in SSO mode, (2) you do not grant anonymous read access, and (3) your OpenID server remembers you.

You have to log out by going to your OpenID server. We can't really get rid of the logout link, because if you do allow anonyomus read access then this feature would work as expected.

If you see this problem where the above 3 assumptions do not hold, please describe your setup in details and reopen this ticket.

Change By: Kohsuke Kawaguchi (27/Nov/13 6:55 PM)
Status: Open Resolved
Assignee: Michael O'Cleirigh Kohsuke Kawaguchi
Resolution: Won't Fix
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to