Does Web Governance provide Single Sign-On (SSO) such as OAuth 2.0?

Web Governance supports SAML 2.0 and Shibboleth Single Sign-on systems, but does not support OAuth 2.0. However, Web Governance customer authentication to the Web Governance platform is done with OAuth2 using the in-house identity provider (IdP).

SSO systems save time for your employees, help you avoid potential issues that can result from lost or forgotten passwords, and lower the risk of password phishing for your company.   

To activate:

1. Contact Acquia Support with a request.

   Provide the following details in the request:

   • An IdP metadata URL address or .xml file

     Note

     If you cannot retrieve your IdP metadata without first knowing the SP metadata, provide rest of the details and proceed to Step 2.   

   • Email address to log in, specifying whether the address is a Name-ID or an attribute.
   • If possible, include the first name and last name in the attributes.

   In response to your request, Acquia Support provide the following details:

   • SP metadata URL
   • ACS URL
   • Login URL
   • Logout URl
   • Entity ID
2. When everything is tested, Web Governance enables enforced SSO.

3. Test SSO in the Web Governance App.

   Consider the following requirements specific to SSO:

   • The person who tests SSO must have a Web Governance account.

   • After successful testing, Web Governance sets up the email domains to enable SSO.

     The configuration works each time you log in to Web Governance.

   • Web Governance can also enforce the SSO by disabling the password sign-on fallback. If SSO does not work, the system provides a password option. 
   • Web Governance does not use automatic provisioning. Therefore, you must have a registered user account in the Web Governance App before you log in through SSO. This is because the standard login process includes counter-checking the user email that is used against existing emails on the user list in Web Governance.