Version Affected: All
Description:
Secureauth using an SP Start URL to move Users to the SP in order to generate an AuthN request when Users have decided to bookmark the IdP page instead of the SP.
Cause:
On SAML realms with custom code, this SP Start URL does not trigger
Resolution:
Move the custom aspx and .vb pages from the Customized folder to the Authorized Folder.
Eg.
1. Take a backup of /Authorized/Saml20SPinitPost.aspx
2. Copy the /Customized/Saml20SPinitPost.aspx and Saml20SPinitPost.aspx.vb to the /Authorized folder
3. Edit the Post Auth page to use our standard Saml SP init by Post option instead of Custom Redirect
Special Considerations
The above example is using the SAML SP Init by Post as an example but the same fix holds true for SAML by redirect too.
SecureAuth Knowledge Base Articles provide information based on specific use cases and may not apply to all appliances or configurations. Be advised that these instructions could cause harm to the environment if not followed correctly or if they do not apply to the current use case.
Customers are responsible for their own due diligence prior to utilizing this information and agree that SecureAuth is not liable for any issues caused by misconfiguration directly or indirectly related to SecureAuth products.
Comments
Please sign in to leave a comment.