Currently, the platform assumes a single SSO method is active, which can lead to inconsistencies when multiple methods, such as SAML and JWT, are configured simultaneously. When both methods are enabled, the platform defaults to prioritize the SAML setup, which redirects anonymous users to the SAML IdP instead of JWT, causing unexpected behavior for users who rely on both SSO methods. To support multiple SSO methods, we should consider implementing the following features: Separate Settings for Each SSO Method : Provide configuration options that allow for distinct settings and triggers for each SSO method (e.g., SAML for internal users, JWT for customers). Customizable Redirection Flows : Allow specific redirection rules based on user groups or SSO type, ensuring that each group is redirected to the appropriate IdP as per their assigned method. Error Prevention and Management : Include guidance or alerts for users if their multi-SSO configuration could lead to conflicts, ensuring they are aware of potential inconsistencies.
