It looks like an attempt at this was made https://github.com/openshift/rhc/pull/486
Would the customer also like to use their x509 cert with the management console?
I realize this is a request for rhc functionality, just wondering if they realize the console is a different kettle of fish.
As long as the the management console follows the same authentication model as the the console and the broker wiring up X509 put to this should not be hard (as httpd offloads the authentication).
I had to look at the actual confs and requests to update my understanding. The console does the authentication and then just passes the user back to the broker. So this will work with x509 auth the same as it would with the broker. So ignore my comment 4.
(In reply to Luke Meyer from comment #4)
> Would the customer also like to use their x509 cert with the management
> I realize this is a request for rhc functionality, just wondering if they
> realize the console is a different kettle of fish.
Yes, the customer would like to use the x509 cert with the management console.
I'm just curious if there has been any progress on this RFE. We are at a point in our deployment where this would be useful.
Please let us know if there is anything you need from the onsite team.
We'll be rebasing the rhc pull request for x509 as soon as possible. It's one of our next highest priority tasks.
(In reply to Eric Rich from comment #3)
> It looks like an attempt at this was made
For what its worth, I implemented the changes in the pull. We've had success getting RHC to do what we need it to do.
*** Bug 1096391 has been marked as a duplicate of this bug. ***
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.