-
Bug
-
Resolution: Fixed
-
Major
-
-
1.0-pre-beta-1, pacific
To reproduce:
- Run blue ocean, open http://localhost:8080/jenkins/blue/pipelines/ - leave open in a tab
- Restart it
- go back to http://localhost:8080/jenkins/blue/pipelines/ and try to click on a pipeline, open it, open a run etc. Keep an eye on browser console and you will see auth errors in the api, but the GUI will not log you in until you refresh the whole page.
- relates to
-
JENKINS-36980 intermittent NPE/500 errors after leaving blue ocean open for a while
-
- Closed
-
[JENKINS-36941] Restarting server (or letting session timeout) will cause hidden auth failures rather than trigger reauth
Epic Link | New: JENKINS-35749 [ 171790 ] |
Description |
Original:
To reproduce: * Run blue ocean, open http://localhost:8080/jenkins/blue/pipelines/ * Restart it * go back to http://localhost:8080/jenkins/blue/pipelines/ and try to click on a pipeline, open it, open a run etc. Keep an eye on browser console and you will see auth errors in the api, but the GUI will not log you in until you refresh the whole page. |
New:
To reproduce: * Run blue ocean, open http://localhost:8080/jenkins/blue/pipelines/ - leave open in a tab * Restart it * go back to http://localhost:8080/jenkins/blue/pipelines/ and try to click on a pipeline, open it, open a run etc. Keep an eye on browser console and you will see auth errors in the api, but the GUI will not log you in until you refresh the whole page. |
Labels | New: mvp |
Sprint | New: 1.0-beta-1 [ 86 ] |
Assignee | New: Vivek Pandey [ vivek ] |
Summary | Original: Restarting server will cause hidden auth failures rather than trigger reauth | New: Restarting server (or letting session timeout) will cause hidden auth failures rather than trigger reauth |
Link |
New:
This issue relates to |
I think this may be related to JWT stuff right vivek ? or at least needs to wait until it lands, so that the GUI can respond accordingly.