[
https://issues.jboss.org/browse/JBDS-3089?page=com.atlassian.jira.plugin....
]
Eric Rich commented on JBDS-3089:
---------------------------------
With JBoss we typically tell customer to follow
https://access.redhat.com/solutions/202263
for setting up there Server's for SSL communication. The process is more or less the
same for clients.
For those clients that want to use there CAC card or a FIPS compliant solution we direct
them through a process like
https://access.redhat.com/solutions/42301
From a UX perspective I think we could leverage other tools like ESC
(
https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/...)
to help get the integration with the right tools people are looking for effectively.
-
https://apps.fedoraproject.org/packages/esc/overview
Note: The CAC / FIPS integration is a lofty goal, and in my opinion a secondary item to
try and achieve.
(however I wanted development to know about it, because if you give a mouse a cookie,
its going to want a glass of milk).
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)