-
Bug
-
Resolution: Done
-
Major
-
4.3.0.Alpha2
-
None
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
- blocks
-
JBIDE-19596 Connection wizard: have to retype password if I want to edit a v3 connection
- Closed
- incorporates
-
JBIDE-19596 Connection wizard: have to retype password if I want to edit a v3 connection
- Closed
- is related to
-
JBIDE-19630 v3 connections: store to default url based persistence vs custom json format
- Closed
-
JBIDE-19412 Cleanup ConnectionURL usage for v3 connections
- Open