[
https://issues.jboss.org/browse/JBIDE-20054?page=com.atlassian.jira.plugi...
]
Jeff Cantrill commented on JBIDE-20054:
---------------------------------------
[~mlabuda] [~adietish] I believe this to only be a UI error. In my tests, if I uncheck
save and then check the storage I see there is no token associated with the given server
and ID. Additionally, I restarted and check the storage to confirm it wasn't being
saved on exit and confirmed the token is not there. The only issue that I believe exists
is the 'remember' checkbox is not properly databound to the value in the
connection. I will make a fix for that.
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: Critical
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)