Apex Code Development You need to sign in to do that
Don't have an account?
Salesforce certificates change from Symantec to DigiCert in January and February 2018
Hi Experts,
Hope some one wil help me:
Salesforce going to update the certificates. Please refer the below Link.
https://help.salesforce.com/articleView?id=000269027&language=en_US&type=1
So Here i have to do the test compatibility in my environment for MiddleWare and Integration:
Can any one please let me know how to perform the below steps:
For Middleware/Integrations
To test the compatibility of an API client that uses SOAP to communicate with Salesforce:
To test the compatibility of an API client that uses REST to communicate with Salesforce:
Raj
Hope some one wil help me:
Salesforce going to update the certificates. Please refer the below Link.
https://help.salesforce.com/articleView?id=000269027&language=en_US&type=1
So Here i have to do the test compatibility in my environment for MiddleWare and Integration:
Can any one please let me know how to perform the below steps:
For Middleware/Integrations
To test the compatibility of an API client that uses SOAP to communicate with Salesforce:
- Set up an API client in a test environment.
- In that test environment, change the API client's login endpoint hostname fromlogin.salesforce.com or [MyDomain].my.salesforce.com tohttps://certtest.force.com.
- As an example, changehttps://login.salesforce.com/services/Soap/u/32.0 to https://certtest.force.com/services/Soap/u/32.0 while leaving the path as-is.
- Log in with that API client.
- If you see an error message that resembles the following: "INVALID_LOGIN: Invalid username, password, security token; or user locked out." or “Content is not allowed in prolog.”, then this test passed and your integration trusts DigiCert-signed certificates.
- The presence of this response means that the underlying TLS connection was successful, despite the higher-level error. The TLS connection is the focus of this test.
- If you instead see an error message that involves TLS or HTTPS, then the test has failed. Your API client will require adjustments to its list of trusted certificate authority certificates to trust DigiCert-signed certificates.
To test the compatibility of an API client that uses REST to communicate with Salesforce:
- Set up an API client in a test environment.
- In that test environment, change the API client's access token retrieval endpoint hostname fromlogin.salesforce.com or [MyDomain].my.salesforce.com to certtest.force.com.
- As an example, changehttps://na1.salesforce.com/services/oauth2/token to https://certtest.force.com/services/oauth2/token while leaving the path as-is.
- Alternatively, it's possible to change the API client's service URL from [instance].salesforce.com or [MyDomain].my.salesforce.com to certtest.force.com.
- As an example, changehttps://na1.salesforce.com/services/data/v32.0/ to https://certtest.force.com/services/data/v32.0 while leaving the path as-is.
- If you see an OAuth error, an "INVALID_SESSION_ID Authorization required" error, or a "400 Bad Request" error, then this test passed.
- The presence of this response means that the underlying TLS connection was successful, despite the higher-level error. The TLS connection is the focus of this test.
- If you instead see an error message that involves TLS or HTTPS, then the test has failed. Your API client will require adjustments to its list of trusted certificate authority certificates to trust DigiCert-signed certificates.
Raj