[JIRA] (JENKINS-36941) Restarting server (or letting session timeout) will cause hidden auth failures rather than trigger reauth
Title: Message Title Michael Neale closed an issue as Fixed This is fixed with the reload on 40X thing Ivan did. So closing it. Effectively a dupe. Jenkins / JENKINS-36941 Restarting server (or letting session timeout) will cause hidden auth failures rather than trigger reauth Change By: Michael Neale Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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
[JIRA] (JENKINS-36941) Restarting server (or letting session timeout) will cause hidden auth failures rather than trigger reauth
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-36941 Restarting server (or letting session timeout) will cause hidden auth failures rather than trigger reauth Change By: James Dumay Sprint: 1.0-pre-beta-1 , 1.0-b07/b08 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36941) Restarting server (or letting session timeout) will cause hidden auth failures rather than trigger reauth
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-36941 Restarting server (or letting session timeout) will cause hidden auth failures rather than trigger reauth Change By: James Dumay Sprint: 1.0-pre-beta-1 , 1.0-b05/b-06 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36941) Restarting server (or letting session timeout) will cause hidden auth failures rather than trigger reauth
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-36941 Restarting server (or letting session timeout) will cause hidden auth failures rather than trigger reauth Change By: James Dumay Sprint: 1.0-pre-beta-1 , 1.0-beta-1 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36941) Restarting server (or letting session timeout) will cause hidden auth failures rather than trigger reauth
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-36941 Restarting server (or letting session timeout) will cause hidden auth failures rather than trigger reauth Change By: James Dumay Sprint: 1.0-pre-beta-1 , 1.0-beta-2 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36941) Restarting server (or letting session timeout) will cause hidden auth failures rather than trigger reauth
Title: Message Title Michael Neale commented on JENKINS-36941 Re: Restarting server (or letting session timeout) will cause hidden auth failures rather than trigger reauth May be fixed by JWT... lets see Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36941) Restarting server (or letting session timeout) will cause hidden auth failures rather than trigger reauth
Title: Message Title Vivek Pandey commented on JENKINS-36941 Re: Restarting server (or letting session timeout) will cause hidden auth failures rather than trigger reauth Michael Neale right, UI should force login if APIs are returning 403 for anonymous user. it should be closed as duplicate of https://issues.jenkins-ci.org/browse/JENKINS-35783? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36941) Restarting server (or letting session timeout) will cause hidden auth failures rather than trigger reauth
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-36941 Restarting server (or letting session timeout) will cause hidden auth failures rather than trigger reauth Change By: James Dumay Sprint: 1.0-pre-beta-1 , 1.0-beta-1 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36941) Restarting server (or letting session timeout) will cause hidden auth failures rather than trigger reauth
Title: Message Title James Dumay commented on JENKINS-36941 Re: Restarting server (or letting session timeout) will cause hidden auth failures rather than trigger reauth This is in scope to fix for the beta - it's a common use case as of Jenkins 2 to have security enabled Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36941) Restarting server (or letting session timeout) will cause hidden auth failures rather than trigger reauth
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-36941 Restarting server (or letting session timeout) will cause hidden auth failures rather than trigger reauth Change By: Michael Neale Priority: Critical Major Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36941) Restarting server (or letting session timeout) will cause hidden auth failures rather than trigger reauth
Title: Message Title Vivek Pandey commented on JENKINS-36941 Re: Restarting server (or letting session timeout) will cause hidden auth failures rather than trigger reauth https://issues.jenkins-ci.org/browse/JENKINS-35783 is where JWT work is happening. I got pulled in to rollbar thing so its more or less in hold state. I expect to get some help from Tom to convert rollbar JS code as js-builder bundler tomorrow to get that wrapped up. If not this week, early next week I should have JWT PR in. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36941) Restarting server (or letting session timeout) will cause hidden auth failures rather than trigger reauth
Title: Message Title Michael Neale commented on JENKINS-36941 Re: Restarting server (or letting session timeout) will cause hidden auth failures rather than trigger reauth Are there JWT tickets this is a duplicate of? I am not sure if JWT is a pre-req for beta (James Dumay?) , but without it, we need a slightly better strategy to at least keep sessions alive, or detect some common scenarios so that the "leave a browser open" experience isn't broken. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36941) Restarting server (or letting session timeout) will cause hidden auth failures rather than trigger reauth
Title: Message Title Vivek Pandey commented on JENKINS-36941 Re: Restarting server (or letting session timeout) will cause hidden auth failures rather than trigger reauth JWT support is still being worked on, nothing related to it is on master yet. Anyways, not sure whats expected in this ticket. Triggering re-auth is beyond scope of blueocean API, its proper jenkins thing. Once we have JWT support, token expiry can be reported in consistent fashion and blueocean UI can trigger auth redirect based on error code. More on this when JWT support is in, it will still be something in UI layer to trigger re-auth etc. not in API. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36941) Restarting server (or letting session timeout) will cause hidden auth failures rather than trigger reauth
Title: Message Title Michael Neale commented on JENKINS-36941 Re: Restarting server (or letting session timeout) will cause hidden auth failures rather than trigger reauth I can see similar things by using stock jenkins auth, and letting it timeout after 30 minutes or so. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36941) Restarting server (or letting session timeout) will cause hidden auth failures rather than trigger reauth
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-36941 Restarting server (or letting session timeout) will cause hidden auth failures rather than trigger reauth Change By: Michael Neale Summary: Restarting server (or letting session timeout) will cause hidden auth failures rather than trigger reauth Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
