Bug 1276237 - documentation missing to set windows console in ssl mode.
documentation missing to set windows console in ssl mode.
Product: Red Hat Directory Server
Classification: Red Hat
Component: Doc-administration-guide (Show other bugs)
Unspecified Unspecified
high Severity low
: ---
: ---
Assigned To: Marc Muehlfeld
Viktor Ashirov
Depends On:
  Show dependency treegraph
Reported: 2015-10-29 04:14 EDT by German Parente
Modified: 2016-11-14 08:27 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2016-11-14 08:27:25 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description German Parente 2015-10-29 04:14:48 EDT
Description of problem:

We see this in upstream documentation:



By default, the console expects your key and cert database files in $HOME/.389-console. On Windows, this is usually something like C:\Documents and Settings\\.389-console. So when you use the NSS command line utilities like certutil and pk12util, use the -d argument like this:

certutil -A -d "C:\Documents and Settings\<username>\.389-console" -n "CA Certificate" -t CT,, -i cacert.asc -a    

for example, to add the CA cert from the file cacert.asc encoded in ASCII (PEM) format. Now your Console running on Windows should be able to use https and ldaps.

It could be nice to have this in RHEL documentation, administration guide. We have it for RHEL console but not for Windows in: 

We have this in

7.3.7. Managing Certificates Used by the Directory Server Console


but it oculd be nice if we could mention just where to install console certs on windows.

 If it is there, I am sorry
Comment 2 Marc Muehlfeld 2016-11-14 08:27:25 EST
The update for Directory Server 10.1 is now available on the Customer Portal.

Note You need to log in before you can comment on or make changes to this bug.