Apex Code Development You need to sign in to do that
Don't have an account?
Jamie Johnson Client certificate with SAML Single Sign-On retirement
We received a notice that our certificate is being retired on August 7th.
Our SSO is Okta.
We asked Okta if this would have an impact on the sign in and this was their reply:
Okta don't validate the signature on the inbound SAML request from SFDC and we only grab the request ID. So I think you're safe on this end.
I want to make sure that we can safely disregard this notice. Okta is the only way our users can access Salesforce. If the retirement of the certificate causes our user to be locked out of OKTA, our users will be down. I apologize ahead of time, I really know very little about certificates and SSO. Thank you for any help.
Our SSO is Okta.
We asked Okta if this would have an impact on the sign in and this was their reply:
Okta don't validate the signature on the inbound SAML request from SFDC and we only grab the request ID. So I think you're safe on this end.
I want to make sure that we can safely disregard this notice. Okta is the only way our users can access Salesforce. If the retirement of the certificate causes our user to be locked out of OKTA, our users will be down. I apologize ahead of time, I really know very little about certificates and SSO. Thank you for any help.