Thanks
--
Buci
------------------------------------------------------------------------
Buci's Profile: http://forums.techarena.in/members/167148.htm
View this thread: http://forums.techarena.in/active-directory/1286054.htm
if you need the distinguishedName to have a relative DN of uid then
you will need to create a class that supports that. If your pkiUser is an
auxiliary class to a User class in your ADAM instance do you have the
scope to define your own user class that has uid as rdn, is this ADAM
instance just to be used for the PKI objects?
Lee Flight
"Buci" <Buci....@DoNotSpam.com> wrote in message
news:Buci....@DoNotSpam.com...
--
Buci
------------------------------------------------------------------------
Buci's Profile: http://forums.techarena.in/members/167148.htm
View this thread: http://forums.techarena.in/active-directory/1286062.htm
you need to decide what you will be using as your user class,
did you import an User class from one of the MS supplied LDFs
or define your own? Looking at the thread it seem like you defined
a pkiUser Structural class, if you have the ldf for that class you
would need to modify it to have rdnattid attribute as uid, for that
top work you will also need to define a uid attribute in your schema.
It would be good to think about which approach to implementation is
going to be best for your deployment as modifying the schema once in
production may be hard work. So for example if you have some standard
LDFs defining pkiUser as an auxiliary class which seems to be what
RFC 4523 has then perhaps the best approach for you would be to define
a user or inetOrgPerson that has uid as rdnattid and keep pkiUser as
auxiliary.
Lee Flight
"Buci" <Buci....@DoNotSpam.com> wrote in message
news:Buci....@DoNotSpam.com...
>