[
https://issues.jboss.org/browse/JBIDE-11222?page=com.atlassian.jira.plugi...
]
Andre Dietisheim commented on JBIDE-11222:
------------------------------------------
The current behaviour is on purpose. We actually want you to be able to use credentials
that differ from what you already have in the console. Btw. If you enter new credentials,
the new user will make it to the console.
What we could do is to skip the verification step (still showing the credentials page, but
not verifying) if you dont change anything. Would this fullfill what you're missing?
Single sign on for OpenShift
----------------------------
Key: JBIDE-11222
URL:
https://issues.jboss.org/browse/JBIDE-11222
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: openshift
Affects Versions: 3.3.0.Beta1
Reporter: Lucia Jelinkova
Assignee: Andre Dietisheim
Priority: Critical
Fix For: 3.3.0.CR1
At the moment, even if you create an account in the OpenShift Console view and store the
credentials, you are forced to verify them during creation of a new application, importing
of existing application and creation of a new server runtime. Is it possible to have just
"single sign on" similar to the way the team repositories works? It would prompt
for password only in case the user didn't store it in secure storage.
There might be of course problem in case there are more accounts. In that case there
could be added the possibility to select one from existing accounts.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira