SAP Knowledge Base Article - Preview

3679201 - Encrypted "sid" parameter length change impacts Azure Service Bus functionality

Symptom

  • The platform uses (Gigya) for single sign-on authentication.
  • The integration retrieves the "sid" parameter from Gigya during login and stores it in a global variable for application redirects.
  • Previously, the "sid" parameter returned a 128-character value, but it is now being returned in an encrypted format of 172 characters.
  • Azure Service Bus (JDK azure-messaging) cannot handle values greater than 128 characters for this parameter.
  • This behavior was observed across all environments
  • The issue impacts the Production system, preventing users from creating new profiles.


Read more...

Environment

  • SAP Customer Data Cloud
  • Identity
  • Consent

Product

SAP Customer Data Cloud all versions

Keywords

SAP Customer Data Cloud, NYC.id, Gigya, single sign-on authentication, sid parameter, encrypted format, Azure Service Bus, JDK azure-messaging, OIDC flow, parameter length change, profile creation issue, production system, rollback changes, flow adjustment , KBA , CEC-PRO , SAP Customer Data Cloud - Identity, - Consent, - Profile , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.