Version Affected: 9.x
The SecureAuth SAML Consumer has been configured on the workflow tab of a realm.
When the 3rd Party IdP sends the SAML, the SAML consumer URL shows
The Debug log for our realm should show the reason for rejection.
Message="VerifySAML - no signature found"
On the IdP that is creating the assertion, you need to ensure that it signs the assertion.
Eg, Look for a setting like this
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.
Please sign in to leave a comment.