The /SamlRequest URL is being accessed repeatedly, leading to the URL access limit being reached in only SAML enabled case.
The SAML URL is triggered instead of displaying the login page, occurring only in cases where both Active Directory (AD)/Lightweight Directory Access Protocol (LDAP) and SAML are enabled.
Fix:
This issue due to internal handling has been fixed now.
ISSUE ID: SD-123584
Resolution:
The fix for the issue has been attached with this article. Check the "Jar Compatibility" section before downloading the fix jar file (.fjar file). Check this link on how to apply the fjar file.
Kindly add the following code in webapps/ROOT/WEB-INF/security/security-publicaccess.xml and restart SDP to increase the throttle limit for SamlRequestServlet URL. Here it's set as 45. You can change to any number you want per minute. <throttles ...
Issue: In some cases, even after configuration and enabling of SAML option, it does not appear in the login page. However, if you notice in login page customization, the SAML option appears. Root cause: Check SAML - Service provider details. ...
Step 1: Open the ADFS management application Step 2: Right-click Relying Party trust and choose Add Relying Party Trust. The Add Relying Party Trust Wizard opens. Step 3: Choose Claims Aware and click Start Step 4: Choose Enter data about the relying ...
Issue: Even if SDP can be accessed with multiple URLs like internal.servicedesk.com and external.servicedesk.com, the SAML response is always received at the same URL that is configured in Alias URL. Fix: The acs_url column in the SAMLSP table can be ...
Issue: SAML login with existing user works, But Error while dynamic user addition. Debug: Additional prints will be printed in the serverout. Steps to get the Debug logs: Download the attached 14500_9205662_SAML_DYNAMIC_USER_ADDITION_DEBUG.fjar file ...