https://bugzilla.redhat.com/show_bug.cgi?id=673266
Description of problem: The problem can be found in the "Manage Certificates" applet of the DS console, under the Server Certs tab. Even though the server has a CA Certificate installed, the "Request certificate from the following Certificate Authority (CA)" radio button remains greyed out. Version-Release number of selected component (if applicable): 1.2.0 How reproducible: Consistently Steps to Reproduce: 1.Attempt to request a certificate from a Certificate Authority 2. 3. Actual results: Not able to request a server certificate Expected results: Automatic certificate requests. The admin shoulf not have to manually request a certificate Additional info: Screen shots attached
batch update to FUTURE milestone
set default ticket origin to Community
Added initial screened field value.
The non-manual certificate request option in Console lists custom CA Console plug-ins. For any items to show up in the list, it requires a custom certificate request wizard plug-in to be implemented in Java. The idea when this was implemented around a decade ago was that one could implement and distribute a custom plug-in that points to their CA and interfaces with it directly. This is still possible to do, but I think it is pretty low priority.
The ideal thing to do would be to implement a plug-in that interfaces with a Dogtag CA. We would need to make it configurable so one could set their host/port information for contacting the CA.
Metadata Update from @rmeggins: - Issue set to the milestone: 389-admin,console FUTURE
Admin server/Console is deprecated, closing ticket...
Metadata Update from @mreynolds: - Custom field reviewstatus adjusted to None (was: Needs Review) - Issue close_status updated to: wontfix - Issue status updated to: Closed (was: Open)
389-ds-base is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in 389-ds-base's github repository.
This issue has been cloned to Github and is available here: - https://github.com/389ds/389-ds-base/issues/67
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Login to comment on this ticket.