This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(57.599999999999994, 10%, 15%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EPN%3C/text%3E%3C/svg%3E)
Hello,
We are having challenges in implementing Login using using SAML with AD B2C and Magento(PHP based application) and are getting the below error
"The request exceeds allowable time to live"
Can you please help us to troubleshoot the issue?
Regards,
Prashant
@Prashant N • This information is very limited for identifying the issue and troubleshooting it. I would suggest collecting Azure Active Directory B2C logs with Application Insights to acquire more details about the issue before trying any troubleshooting steps.
Hello
We have requested Customer to share the Azure Active Directory B2C logs with Application Insights, will share as soon as we get it.
In the mean time attaching the logs we generated from the applications, attaching the same for your reference. let us know if you find anything.
SAML Request:
<samlp:AuthnRequest xmlns:samlp="urn:oasis:names:tc:SAML:2.0:protocol"
xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion"
ID="ONELOGIN_a17819a2d230984615c6cb625937317db289f63f"
Version="2.0"
IssueInstant="2021-11-10T13:04:22Z"
Destination="https://bekaertcomdev.b2clogin.com/bekaertcomdev.onmicrosoft.com/B2C_1A_signup_signin_saml/samlp/sso/login"
ProtocolBinding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST"
AssertionConsumerServiceURL="https://dev-store.bekaert.com/sws_b2c_english/sso/saml2/acs"
<saml:Issuer>https://dev-store.bekaert.com/sws_b2c_english/sso/saml2/metadata</saml:Issuer>
<samlp:NameIDPolicy Format="urn:oasis:names:tc:SAML:2.0:nameid-format:persistent"
AllowCreate="true"
/>
</samlp:AuthnRequest
@Prashant N · Thank you for your confirmation on This Thread that this issue is resolved after collecting Azure Active Directory B2C logs with Application Insights to get more details about the error. Usually, this happens due to the time difference (clock skew) between the application sending the SAML request and B2C. Make sure there are no more than ±5 minutes of difference.
-----------------------------------------------------------------------------------------------------------
Please "Accept the answer" if the information helped you. This will help us and others in the community as well.