Certificate attributes for Smart Card Logon



Hi,

I set up smart card logon to my windows 2003 domain for XP clients. I use a
AD-integrated Microsoft Enterprise CA 2003 as issuing CA. My domain
controllers each already have their own certificates.

Question: the default certificate templates "smartcard logon" and "smartcard
user" both have the key usage settings "digital signature" and "allow key
exchange only with key encryption (key encipherment)" set. However, the
knowledge base article
http://support.microsoft.com/default.aspx?scid=kb;en-us;281245 explains that
smart card certificates only need the "digital signature" key usage
attribute. But further down, the article also says that "...Smartcard logon
certificates must have a Key Exchange(AT_KEYEXCHANGE) private key type...".

However, I tested both with and without "allow key exchange only with key
encryption (key encipherment)" set and both types of certificates work for
smart card logon!

So is there anybody out there who can tell me if smart card logon
certificates necessarily need the "key encipherment" attribute?

Thanks,
Chris

PS: we intend to use the same certificate for S/MIME signing (but not
encryption). So if "key encipherment" is set, this certificates can
unfortunately also be used for S/MIME encryption. So it would be nice if
smart card logon reliably works without the "key encipherment" attribute...


.



Relevant Pages

  • Re: Certificate attributes for Smart Card Logon
    ... email signature but also email encryption (Microsoft makes no ... "allow key exchange only with key encryption (key encipherment)" is not ... These are V1 multipurpose certificates. ... If you enable the Smart Card Logon, Client Authentication, and Secure ...
    (microsoft.public.windows.server.security)
  • Re: Certificate attributes for Smart Card Logon
    ... signature but also email encryption! ... If you enable the Smart Card Logon, Client Authentication, and Secure ... controllers each already have their own certificates. ...
    (microsoft.public.windows.server.security)
  • Re: Certificate attributes for Smart Card Logon
    ... unfortunately, as far as I know if you have the "Secure Email" application Policy set, a certificate by default may not just be used for email signature but also email encryption! ... If you enable the Smart Card Logon, Client Authentication, and Secure Email application Policies, this ensure that the smart card cannot be used for actual encryption. ... My domain controllers each already have their own certificates. ...
    (microsoft.public.windows.server.security)
  • Re: Certificate attributes for Smart Card Logon
    ... Just ensure that on the Request Handling tab that the Purpose is set to Signature and Smartcard logon. ... If you enable the Smart Card Logon, Client Authentication, and Secure Email application Policies, this ensure that the smart card cannot be used for actual encryption. ... My domain controllers each already have their own certificates. ...
    (microsoft.public.windows.server.security)

Quantcast