In a SAML 2.0 federation architecture, the Service Provider (SP) returns a 403 error during the assertion consumption phase. After verifying the digital signature, what is the most likely cause?
Trap 1: Encryption algorithm mismatch
This would lead to a failure to decrypt the assertion, preventing the process from reaching the 403 stage.
Trap 2: Expired metadata
Metadata expiration usually causes a handshake failure, not a 403 after assertion processing.
Trap 3: Assertion Consumer Service (ACS) URL mismatch
This typically results in a 400 Bad Request or a failure to post the assertion.
- A
Encryption algorithm mismatch
Why wrong: This would lead to a failure to decrypt the assertion, preventing the process from reaching the 403 stage.
- B
Expired metadata
Why wrong: Metadata expiration usually causes a handshake failure, not a 403 after assertion processing.
- C
Assertion Consumer Service (ACS) URL mismatch
Why wrong: This typically results in a 400 Bad Request or a failure to post the assertion.
- D
Subject NameID mismatch
A mismatch in the unique identifier mapping often results in the SP rejecting the session due to unknown identity.