Forum Discussion
Hamish
May 13, 2010Cirrocumulus
Oh... If you've re-imported a new cert for an existing key, the system doesn't know the cert has changed (It's still using the cached copy).
I'm not sure how long the tmm will cache it for either... Maybe forever... (I saw a fix in 10.2.0 for cached certs, but didn't read it fully to see if it would fix the problem you're seeing).
You may have to force a change... If you copy the clientssl profile to a new one (i.e. different name, same parameters, cert & key) and then change the profile on the VS it should force tmm to load the new copy of the cert... You can then change the profile back to the original one and remove the copy.
H