Using the function import of SAP SuccessFactors, you can check the certificate type currently used for SSO. Sample call for Hub configuration GET https://apisalesdemo8.successfactors.com/odata/v2/getSFIDPCertType?acsurl='https://cas-us2.wfs.cloud/auth/realms/demo_box_54/broker/successfactors/endpoint/' Response {"acsurl":"https://cas-us2.wfs.cloud/auth/realms/demo_box_54/broker/successfactors/endpoint/","certType":"sha1","module":"workforce"} Success Sample call for WT&A configuration GET https://apisalesdemo8.successfactors.com/odata/v2/getSFIDPCertType?acsurl='https://demo-demobox54-demo.wfsaas.com.wfsaas.com/workforce/SSO.do?%26RelayState=True' Response {"acsurl":"https://demo-demobox54-demo.wfsaas.com.wfsaas.com/workforce/SSO.do?&RelayState=True","certType":"sha1","module":""} Success 3 For WTA customers: After completing the configuration settings on WFS tenant, please update the module name and the certType on the connected SAP SuccessFactors tenant. The below sample call is for Hub configuration, please follow the same format for WT&A configuration by replacing the acsurl. Sample call for WTA configuration POST https://apisalesdemo8.successfactors.com/odata/v2/updateSFIDPCertType Request body { "acsurl": "https://cas-us2.wfs.cloud/auth/realms/demo_box_54/broker/successfactors/endpoint/", "module":"workforce", "certType":"sha2" } Response Success Note: Please look into this blog to understand the URL pattern for the acsurl "https://workforcesoftware.force.com/customers/s/article/SAP-and-T-A-Steps-needed-to-embed-the-WFS-Suite" - Needs WorkForce community login credentials.