[
https://issues.jboss.org/browse/JBDS-3089?page=com.atlassian.jira.plugin....
]
Eric Rich commented on JBDS-3089:
---------------------------------
RHC does not use a keystore or truststore (its a ruby script not a java application).
Currently
https://bugzilla.redhat.com/show_bug.cgi?id=1089703 is tracking this for RHC.
Based on this it seems that RHC plans to use the x509 certificates (PEM) based files
directly, in this case we may want to follow Eclipses Guidelines for access user keystores
or creating one for the user for this feature.
http://wiki.eclipse.org/Security:_KeyStore_support_for_Eclipse
Note: some customer (DOD, Public Sector) may want this feature to work with there CAC
(Common Access Card's) so you may need to allow for something like
http://stackoverflow.com/questions/752890/how-to-connect-to-https-server-...
following
http://docs.oracle.com/javase/1.5.0/docs/guide/security/p11guide.html as a point
of reference. << not this requires you configure the JVM that Eclipse uses.
x509 Authentication to OpenShift
--------------------------------
Key: JBDS-3089
URL:
https://issues.jboss.org/browse/JBDS-3089
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: openshift
Affects Versions: 8.0.0.Beta3
Reporter: Eric Rich
Assignee: Max Rydahl Andersen
Labels: authentication, ssl
Fix For: 8.0.x
Currently customers are asking for RHC to support x509 Authentication with the broker
service (
https://bugzilla.redhat.com/show_bug.cgi?id=1089703). The same is being asked of
JBDS
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)