[jbosstools-issues] [JBoss JIRA] (JBIDE-19905) Connection token and authentication scheme are not saved
Andre Dietisheim (JIRA)
issues at jboss.org
Wed Jun 3 17:57:02 EDT 2015
[ https://issues.jboss.org/browse/JBIDE-19905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13073896#comment-13073896 ]
Andre Dietisheim commented on JBIDE-19905:
------------------------------------------
If I now refresh the connection, the connection dialog pops up empty, no OAuth token nor username/password are filled-in:
!after-refresh-no-token.png!
!after-refresh-no-username-pw.png!
# EXEC: switch to "Basic" and fill in username and password
Result:
Connection now authenticates successfully, the resources are loaded.
# EXE: Edit your connection
Result:
Now the token is filled-in. OK
!edit-after-username-pw-provided.png!
> Connection token and authentication scheme are not saved
> --------------------------------------------------------
>
> Key: JBIDE-19905
> URL: https://issues.jboss.org/browse/JBIDE-19905
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Jeff Cantrill
> Assignee: Jeff Cantrill
> Fix For: 4.3.0.Beta1
>
> Attachments: after-refresh-no-token.png, after-refresh-no-username-pw.png, edit-after-username-pw-provided.png, unauthorized.png
>
>
> Fix saving of a user's token and the auth scheme for a server. Might consider setting the username for a connection to user.getName() instead of user.getFullName()
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
More information about the jbosstools-issues
mailing list