function readOnly(count){ }
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
+ Start a Discussion
JasoN ZhanG 4JasoN ZhanG 4 

Some questions about the notification that Salesforce Client Certificate will be  Impacted by Upcoming Microsoft Windows Update

We got one notification that Salesforce Client Certificate will be  Impacted by Upcoming Microsoft Windows Update in this link :https://help.salesforce.com/apex/HTViewSolution?urlname=Salesforce-Client-Certificate-Impacted-by-Upcoming-Microsoft-Windows-Update&language=en_US&?d=701300000021Jky&eid=ss-tc 

And have some questions

questions  for the impact :
1. 
Delegated authentication – how to know if we are using this feature ? from which page we can check if we are using this feature ?

2. SAML with default certificate – How to know if we are using this feature ? from which page we can check if we are using this feature ?
 We implemented SSO in Remedyforce ,  so if we don't updated the certificate , the users will noe be able to login to Remedyforce via SSO link ,right? 
3. 
Workflow outbound messages  - how to know if we are using this feature ? so if we don't update , all the notification emials  sent  by the workflow rule , email alert will not be able to send to the  users , right?
4.
AJAX proxy - how to know if we are using this feature ?   this is called by some applicaitons created on our side ,right? 
5.PageReference.getContent() and PageReference.getContentAsPDF() - how to know if we are using this feature ?   this is called by some applicaitons created on our side ,right? 

Questions for the Action :

1.we already have one Salesforce self-signed client certificate which is created at 2/2/2015 and used in our SSO link  , not sure if we need created another one and set it as the API Client Certificate in the API Client Certificate section in the Certificate and Key Management page  ?
2. In the Single Sign-On Settings page , We can't find the Enable Multiple Configs button , and in the  SAML Single Sign-On Settings  , we used the self-signed client certificate we created above as the Assertion Decryption Certificate, not sure if we need to change it ? 
 

JasoN ZhanG 4JasoN ZhanG 4
User-added image
JasoN ZhanG 4JasoN ZhanG 4
User-added imageUser-added image
Chris SweetChris Sweet
I'm working through this right now as well. From what I've found, if you've already enabled "Multiple Configs" in the past, then you'll see the "Assertion Decryption Certificate" option and the "Multiple Configs" button will no longer be visible.
JasoN ZhanG 4JasoN ZhanG 4
Thanks for your support ! So it seems in our Single Sign-On Settings page , we already Enabled Multiple Configs and use the self-signed client certificate we created at 2/2/2015 , so we don’t need update the Single Sign-On Settings for this Microsoft Windows Update ,right? And In the API Client Certificate section of the Certificate and Key Management setup page, can we change the existed self-signed client certificate we created at 2/2/2015 as our org's API client certificate? or we need create another new self-signed client certificate , and set it as the API client certificatein the In the API Client Certificate section of the Certificate and Key Management setup page ? Thanks & Best regards Jason