[Pki-users] LDAPs +TPS questions (CS 8.0)

Adewumi, Julius-p99373 Julius.Adewumi at gdc4s.com
Fri Nov 20 16:48:45 UTC 2009


Sean,
    I would try the similar param in CA,TKS such as :
 
internaldb.ldapauth.authtype= BasicAuth
internaldb.ldapauth.clientCertNickname=
internaldb.ldapconn.port=389
Internaldb.ldapconn.secureConn=false
 
Hope it works.  There are several things in RedHat manual which I have
found to be
not functioning, or rather we couldn't make them to function. Lukily,
for my project, 
we moved to Microsoft CA.

From: Julius Adewumi 
@GDC4S.com 
Ph:480-441-6768 
Contract Corp:MTSI 

 

________________________________

From: pki-users-bounces at redhat.com [mailto:pki-users-bounces at redhat.com]
On Behalf Of Veale, Sean
Sent: Friday, November 20, 2009 8:53 AM
To: pki-users at redhat.com
Subject: [Pki-users] LDAPs +TPS questions (CS 8.0)




Hello, 

I'm trying to enable ssl client authentication with the internal
database for the TPS. 

Using the Administrator Guide chapter 13.5.2, I've successully enabled
ssl client authenticatoin to the internal database for the CA, DRM, and
TKS.

However, the final step 11 of 13.5.2 requires the modification of CS.cfg
paremeters: 
internaldb.ldapauth.authtype 
internaldb.ldapauth.clientCertNickname 
internaldb.ldapconn.port 
Internaldb.ldapconn.secureConn 

All of which are missing from TPS CS.cfg, and I can't seem to find any
corresponding parameters. 

First off, has this feature been implemented with the TPS? 

If so, what are the corresponding CS.cfg parameters? Or what parameters
should I change elsewhere? 

Thanks 

Sean 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/pki-users/attachments/20091120/a5d653cf/attachment.htm>


More information about the Pki-users mailing list