[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: User database requirements for PKINIT

There are several modes of operation with PKINIT. One
envisions the KDC issuing tickets to users who lack KDB
principal records but who have trusted certs; in this mode the
users get principal names based on their certs' names. Another
envisions using PKI merely for pre-authentication, but with
the user needing to have a principal.

I know little about the Heimdal beta PKINIT implementation,
but from what you say I'd imagine it does not support user
principal-less PKINIT, yet.



> -----Original Message-----
> From: Christopher James [mailto:cjames@berkeley.innomedia.com]
> Sent: Thursday, May 23, 2002 3:40 PM
> To: heimdal-discuss@sics.se
> Subject: User database requirements for PKINIT
> I am runing  Heimdal with the pre-beta PKINIT patch (posted May 15
> 2002).
> To get it to work with a principal, I first had to add the 
> principal to
> the database
> using the kadmin add command.  If the principal is not in the 
> data base
> when I
> send an AS-REQ message (with pkinit), I recieve a KRB_ERROR message
> with "client unknown".   Is this the expected behavior - in 
> other words
> must
> the principal be in the database before an AS-REQ  (with pkinit) will
> work (for
> this version and future versions of PKINIT).  Thanks.
> Christopher

Visit our website at http://www.ubswarburg.com

This message contains confidential information and is intended only 
for the individual named.  If you are not the named addressee you 
should not disseminate, distribute or copy this e-mail.  Please 
notify the sender immediately by e-mail if you have received this 
e-mail by mistake and delete this e-mail from your system.

E-mail transmission cannot be guaranteed to be secure or error-free 
as information could be intercepted, corrupted, lost, destroyed, 
arrive late or incomplete, or contain viruses.  The sender therefore 
does not accept liability for any errors or omissions in the contents 
of this message which arise as a result of e-mail transmission.  If 
verification is required please request a hard-copy version.  This 
message is provided for informational purposes and should not be 
construed as a solicitation or offer to buy or sell any securities or 
related financial instruments.