[
https://issues.jboss.org/browse/TEIIDDES-1591?page=com.atlassian.jira.plu...
]
Rob Stryker commented on TEIIDDES-1591:
---------------------------------------
I think this would fit nicely in org.jboss.tools.foundation. Unfortunately, foundation is
not yet created ;) (There's a PR for it).
Foundation is intended to be a new location for all sorts of well-tested utilities, split
up by framework (platform, wtp, egit, etc). It's an effort to get our code under
strict organization (we'll see how that works ;))
However, for this dialog to be placed there, I think we shouldn't mention JBossTools
or Teiid Designer specifically. I think we should be more vague and state that
"Several installed features use secure storage for storing passwords and other
sensitive data."
There's no harm to this, and it ensures that our lowest level plugin is agnostic as to
what is running along-side it, whether its JBT, JBDS, TD, etc.
Improve the default eclipse dialog for entering the secure storage
password
---------------------------------------------------------------------------
Key: TEIIDDES-1591
URL:
https://issues.jboss.org/browse/TEIIDDES-1591
Project: Teiid Designer
Issue Type: Enhancement
Components: Eclipse Integration
Affects Versions: 8.1
Reporter: Paul Richardson
Assignee: Max Rydahl Andersen
Fix For: 8.2
Attachments: password-provider-dialog.jpg
Both JBossTools and Designer use secure storage for storing passwords. As such, when
opening the application and accessing secure storage for the first time (usually on
starting a JBoss server), the default password dialog is displayed. However, this dialog
is unintuitive since it provides little explanation of what password it is requesting and
is easily confused for the JBoss / Teiid admin password or the Teiid jdbc password.
Ironically, this password will allow access to both of them!
Investigation shows that the default password provider can be overridden using the
org.eclipse.equinox.security.secureStorage extension point.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira