[
https://issues.jboss.org/browse/JBIDE-20054?page=com.atlassian.jira.plugi...
]
Andre Dietisheim commented on JBIDE-20054:
------------------------------------------
This sounds rather serious since security related. Tokens do expire and one with the token
only cannot create a new one. Still, I'm wondering if this isnt serious enough for
4.3.0.Beta1 resplin-a
[~maxandersen] your take?
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
Priority: Minor
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)