we run a Win2008R2-based AD-integrated PKI and Exchange 2016 on-premise. Due to an user-autoenroll certificate policy, an email-signing and encryption certificate is issued and published in AD. From what I understand these certificates are also finally linked to the user in GAL and OAB of Exchange/Outlook.
I have some questions re. this:
- why are expired certificates still kept in AD. Actually I feel like only one expired and the valid one are kept, so I have usually 2 certificates for each user (except the user is quite new). Am I right?
- Recently, but still about one week ago, I have deleted some certificates from my AD user account in order to only keep eon certificate which is valid and the right one. I have had some issues with mail encryption while I played around with requesting certificates to my own user account, and once I was done I deleted all published certificates from my AD account,hoping that in the GAL/OAB only my one and only valid certificate will apply. But if I now have a look to the Exchange Address Book and import my contact to Outlook, I still always have two certificates there, the correct one and the previous one, which is even set as default. This issue is discussed here https://social.technet.microsoft.com/Forums/en-US/88dd81be-d077-41c0-a268-2d62239f3aa2/messed-up-email-security-certificate-information-with-adpkiexchange-for-an-user?forum=Exch2016MFSM
- All the other users which really have two certificates published in AD, but one is expired, also have this expired one set as default in GAL/OAB (I can actually only figure this out if I start importing the Exchange Address Book User as a contact into Outlook). Why is always the expired certificate still there and why is it always set as the default one?
- shouldn't GAL/OAB 1:1 reflect the AD-published user certificates re. email-signing and encryption, in GAL/OAB? How can I tell which public key of an user I am using from GAL/OAB in order to sign an email message?
- can anyone tell me how user certificate auto-enrollment renewal works? Does the user only get a new certificate based on the existing private key? Or is a whole pair re-issued? I am asking, because I wonder what will happen with messages one has received 3 years ago if he now has a new private key (and has not baked up the old one)?
kind regards,
Dieter Tontsch