Control Certificate selection
this dual ca environment 1 ca retired. dual implementation due poor original ca2003 implementation , replaced new considered ca 2008 environment. the ca2003 provisioning for certificates was turned down 30 days ago. fine except 1 "user experience" problem
the original ca2003 user certificates , new ca2008 user certificates are able be used device/user verification mechanism vpn access (juniper) "user experience" issue the pop-up being presented in the browser window when authenticating, choice of using either certificate. prior delivery of user 2008 certificate, transparent. user not asked choice of certificates. question/conundrum.
i have thought of different options , none pretty. other than:
1. manual move of ca2003 user certificate trusted people store site support/help desk staff or
2. changing ca2003 user template not not renew with a very short lifespan, enable ca2003 new user template and force renewal of ca2003 user certificates or
3. convoluted powershell script interrogate the personal user store certificates ca2003 certificate template , initiate a transfer trusted people folder.
is there cleaner option can consider or pursue. my initial solution a. provide awareness b. fix sr mgmt , call service desk. c. let problem disappear ca2003 user certificates expire. solution has not made friends , tasked find better mousetrap. solutions/suggestions gladly accepted
once have multiple certificates in store, can't automatically select one, hence choice prompt.
you can define old user certificate template superseded new user certificate template; force old certificate removed , replaced. http://technet.microsoft.com/en-us/library/cc753044(v=ws.10).aspx
cheers
jj
jason jones | forefront mvp | silversands ltd | blogs: http://blog.msedge.org.uk , http://blog.msfirewall.org.uk
tried , discovered partial/minimal success. i think know the cause. if the certificate provisioned. template change has no impact existing provisioned provided certs. think i may need force renewal cause renewal. next step, here come
thanks, should have thought of this. provide update if solves.
Windows Server > Security
Comments
Post a Comment