![]() |
sponsored links |
|
|
sponsored links
|
|
|
4
19th August 09:33
External User
Posts: 1
|
In article <eps2fPDuEHA.3860@TK2MSFTNGP09.phx.gbl>, seaedsit@hotmail.com
says... The solution is to use two certificate templates. The first, for initial enrollment only allows the couple of admins to enroll on behalf of the user. This is accomplished by limiting permissions to the enrollment agents and to require the certificate request agent OID in the signing certificate. This certificate can include a custom application policy OID designated as the "Company" smart card Then you can create a renewal certificate that: - supercedes the initial certificate - enables Read, Enroll, and Autoenroll perms to *all* smart card holders - Requires that the request be signed with an application policy OID, the "Company" smart card OID. HTH, Brian Ths |
|