[
https://issues.jboss.org/browse/JBIDE-20054?page=com.atlassian.jira.plugi...
]
Andre Dietisheim edited comment on JBIDE-20054 at 6/29/15 12:39 PM:
--------------------------------------------------------------------
[~jcantrill] this was a higher prio bug since one could not easily remove the token from
secure storage and security related issues are generally looked at in higher prios.
I verified it, it works for me, the token is now correctly removed from secure storage if
I uncheck the checkbox.
merging and pushing to upstream/master
was (Author: adietish):
[~jcantrill] this was a higher prio bug since one could not easily remove the token from
secure storage and security related issues are generally looked in higher prios.
I verified it, it works for me.
merging and pushing to upstream/master
Connection wizard: Cannot remove secure storage of v3 connection
token
----------------------------------------------------------------------
Key: JBIDE-20054
URL:
https://issues.jboss.org/browse/JBIDE-20054
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.3.0.Beta1
Reporter: Marián Labuda
Assignee: Jeff Cantrill
Priority: Minor
Labels: openshift_v3
Fix For: 4.3.0.Beta2
If I create a new v3 connection with OAuth authentization method and choose to store
token in secure storage (or I edit the existing one connection with token and check the
checkbox to store the token in secure storage), token is stored. But if I decide later to
prevent it to being stored by unchecking the checkbox in Edit connection dialog, it does
not work. If I uncheck the checbox and hit the Finish button and come back to edit
connection dialog, the checkbox is still checked. This is related only to OAuth
authentization method (basic authentization method works as expected).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)