[jbosstools-issues] [JBoss JIRA] (JBIDE-20513) tricky to login to openshift when token expires
[
https://issues.jboss.org/browse/JBIDE-20513?page=com.atlassian.jira.plugi...
]
Jeff Cantrill commented on JBIDE-20513:
---------------------------------------
The expiration would be related to the value configured by the auth service; we can't
control that. In regards to how 'oc' works, are you auth'ing against a system
set-up to use basic auth? The auth flow in general needs to be refactored to conform what
happens in the 'oc' client. I believe there is an open issue against the rest
client to address.
tricky to login to openshift when token expires
-----------------------------------------------
Key: JBIDE-20513
URL: https://issues.jboss.org/browse/JBIDE-20513
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Reporter: Max Rydahl Andersen
Priority: Critical
Fix For: 4.3.1.CR1
I logged in with token.
24hrs later I start eclipse and expand the connection in explorer
expecting to just login.
Here is what happens instead:
a) info message (not error) is logged to error log hiding the explorer view
b) after some seconds (seems there is a timeout) a login dialog comes up saying I need to
sign in (no clear info that auth failed or token missing etc.).
cancel the dialog since I'm trying to figure out what happened.
c) Now the explorer just shows "You must obtain API token by visiting ..." as
child and I cannot see straightforward way to log in again.
Turns out Refresh does trigger login again.
meanwhile command line 'oc' seem to be fine at logging in with token older than
24 hrs...can't verify that though, but in any case:
a) do a user really need to re-login every 24 hours ?
b) the error handling/dialogs shown are not very informative
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)