eSignature for Approvals is Requiring an Additional Single Sign-on (SSO)Issue In this example the eSignature for Approvals functionality is configured for Change Requests. The Customer has Azure Single Sign-on (SSO) setup and working. When users complete their Approvals, it is requiring another SSO (in a pop-up screen) to compete the approval.CauseThe Force AuthnRequest attribute is enabled.Resolution1. The issue is caused by the 'Force AuthnRequest' attribute being enabled on the Identity Provider (IDP) in the SAML 2.0 configuration using Multi-Provider SSO. This forces SSO authorization login again when presented with any auth checks, even if logged in the session already. 2. Note: If you are using the eSignature functionality, the Force AuthnRequest attribute is required, or e-signature is not supported.