SP Initiated transaction is failing with BAD_SAML_REQUEST_ENCODING

Products

• CA Single Sign On Agents (SiteMinder)
• CA Single Sign On Federation (SiteMinder)
• CA Single Sign On Secure Proxy Server (SiteMinder)
• CA Single Sign On SOA Security Manager (SiteMinder)
• SITEMINDER
• VCF Site Reliability Engineering
• VMware Site Recovery Manager 8.x
• VMware vCenter Site Recovery Manager 5.x

Issue/Introduction

Session store schema missing the required schema to support the SP initiated transactions.

[09/17/2024][04:43:49][15588][139994290833152][104ad68d-ba5bffc6-58aad80a-31364a93-2057a809-466][SSO.java][doGet][Transaction with ID: 104ad68d-ba5bffc6-58aad80a-31364a93-2057a809-466 failed. Reason: BAD_SAML_REQUEST_ENCODING] [09/17/2024][04:43:49][15588][139994290833152][104ad68d-ba5bffc6-58aad80a-31364a93-2057a809-466][SSO.java][doGet][The SAMLRequest parameter was not encoded properly.] [09/17/2024][04:43:49][15588][139994290833152][104ad68d-ba5bffc6-58aad80a-31364a93-2057a809-466][SSO.java][doGet][Ending SAML2 Single Sign-On Service request processing with HTTP error 400] [09/17/2024][04:43:49][15588][139994290833152][104ad68d-ba5bffc6-58aad80a-31364a93-2057a809-466][ErrorRedirectionHandler.java][redirectToErrorPage][Sending HTTP Error 400 ]

Environment

12.8.x

Cause

The current sessionstore could be missing the schema structure.

Resolution

Recreating the Sessionstore schema using the script available in your current PolicyServer version fixed the issue.

<PolicyServer_Home>/db