[
https://issues.jboss.org/browse/JBIDE-19549?page=com.atlassian.jira.plugi...
]
Andre Dietisheim updated JBIDE-19549:
-------------------------------------
Description: Currently v3 connections store the authentication tokens in plaintext
into some configuration file. We should store them to the secure storage. Passwords are
not stored at all, we should make sure that if a user is editing his v3 connection he does
not have to retype his password and have it provided from secure storage (was: Currently
v3 connections store the authentication tokens in plaintext into some configuration file.
We should store them to the secure storage.)
Connection wizard: v3 connection should store tokens and passwords to
the secure storage
----------------------------------------------------------------------------------------
Key: JBIDE-19549
URL:
https://issues.jboss.org/browse/JBIDE-19549
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.3.0.Alpha2
Reporter: Andre Dietisheim
Currently v3 connections store the authentication tokens in plaintext into some
configuration file. We should store them to the secure storage. Passwords are not stored
at all, we should make sure that if a user is editing his v3 connection he does not have
to retype his password and have it provided from secure storage
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)