SAP SuccessFactors failing with SAML Timeout
Answered
Which connector?:
https://fivetran.com/dashboard/connections/barrette_unbraided/settings?groupId=spectral_midnight&service=sap_success_factors
Connector name: SAP SuccessFactors
Additional details:
This connection keeps failing with this error
- Failed to refresh credentials. Failed to fetch token from path [https://api41preview.sapsf.com/oauth/token/], status code [400], response [{"errorHttpCode":"400","errorMessage":"The SAML assertion has expired. validNotBefore: 2026-08-26T15:24:27.651Z. validNotOnOrAfter: 2026-08-26T15:39:27.651Z. For more information, see https://help.sap.com/docs/SAP_SUCCESSFACTORS_PLATFORM/d599f15995d348a1b45ba5603e2aba9b/4e27e8f6ae2748ab9f23228dd6a31b06.html."}]
The SAML Assertion expires every 20 minutes and the connector fails. The documentation says this
- If the SAML assertion expires, then you must create a new assertion token, re-authenticate the connection, and start the sync before it expires.
The upstream limitation is this. is there a suggested workaround or any improvements to the connector that can remove dependency on the SAML token?
-
Official comment
Hi Sreekar,
Thank you for reaching out with your request regarding the SAP SuccessFactors connector. Currently, addressing the SAML timeout issue is not on our immediate roadmap. We recommend upvoting this feature in our community forum, as it helps us prioritise based on user interest. While we cannot provide any timelines, your feedback is valuable for future consideration.
Best,
Sanjeevv Maniram -
Fivetran uses client id, company id and SAML Assertion to generate access token but its so faulty mechanism because the SAML default expiry is around 10- 20 mins when you generate. The work around is to generate your assertion in local with custom expiry. You can use sf oauth api to generate it.
Please sign in to leave a comment.
Comments
2 comments