Setting up SSO for Azure AD
  • 19 Jan 2023
  • 3 Minutes to read
  • Dark

Setting up SSO for Azure AD

  • Dark

Setting up Single Sign-On involves very detailed settings, and every provider and customer environment is different.  If a user is inexperienced with SSO, it may take several attempts to get all the identifying data and settings correct to allow for secure and reliable authentication.  It is recommended to make sure someone in the organization with experience in SSO and IT infrastructure is available to streamline the process. Decisions support team is available to help but may not be able to answer questions or solve problems unique to a company.

Decisions allows users to use Single Sign-On for Azure Active Directory using Azure and the SAML Module.


  • Azure iDP configured within Portal.
  • Azure application (Non-Gallery App). 
  • A metadata document from the application in Azure.
  • SAML Module installed. To learn more on installing modules, see Installing Modules in Decisions.
Accounts created before the SAML module is installed will need to be updated before using Single Sign-On. Please contact support on how to update the account. Learn how to modify accounts after setting up SSO in the SSO Basics article.


  1. In Azure, ensure that the correct endpoint URL is added to the Reply URL (Assertion Consumer Service URL) field.
  2. In Decisions Studio, navigate to System > Settings, right-click SAML Settings, and select Edit.
  3. From the Edit SAML Settings window, check the Enabled box. Then, under Identity Providers, click ADD.
  4. From Add Identity Providers, provide a Display Name. Under Metadata Document Preference, select Fetch Metadata From URL. Then, map the applicable Metadata via the chosen method. 
    The Metadata URL is generated by the AD server and is a required input. Providing it will automatically fill in all fields of the Module except for the SP Issuer ID, which is the Portal Base URL.

    The screenshot below is an example of the Azure Portal to demonstrate where to find the metadata URL for a created app.

  5. Under the PROCESS IF USER NOT FOUND category, select Run Flow In Background. Under Run Flow, click PICK OR CREATE FLOW and pick SAMLDefaultCreateAccount.
  6. If manually configuring the module, click ADD under X.509 Certificates, and add a valid x509 Certificate. Click OK. If the metadata URL were used, the X.509 certificate would automatically be pulled.  
    For more information on x.509 Certificates, see What is an x509 Certificate? 

  7. In the Edit SAMLSettings window, select the newly added Identity Provider from the Primary Identity Provider list. Save once the Primary Identity Provider has been configured.
    Log SAML Requests & Responses is an optional setting that should only be enabled when troubleshooting. Ensure that this setting is disabled otherwise. Once enabled, the location for the SAML logs can be found at C:\\Program Files\Decisions\Decisions Server\Logs

Enabling SSO

Before enabling SAML SSO, configure at least one Admin user to work with SAML SSO or else there will be no admin users who can log into the system after enabling. When SSO is enabled, no local users can log in. If this is accidentally done, disable SSO and then log in with local users.
  1. Navigate to C:\Program Files\Decisions\Decisions Server and open the Settings.xml in a Text Editor.
  2. Locate the <EnableSingleSignOn> line and change the false value to true. Save and close the file.
  3. Restart the Decisions Server
  4. Continue testing on an Incognito Session; use the first open session to uncheck the Enabled button in the SAML module should something not work. 
    This saves users from setting EnableSSO to false and restarting the Decisions Server again.


If a user wants to convert a local account to a SAML/SSO account or if a user receives errors when updating the User Identifier:

  • Modify the UserID of the account
  • Use SQL to modify the entity_account table and change the type of account
  • Create a new account after SAML has been turned on and add it to the admin group

If the redirect is working only on a refresh of the initial login:

  • Check the Retry on Log-In checkbox
  • Ensure “/Login” is at the end of the Sign-On URL (case-sensitive)

When there is a "Context can only be used from localhost" error:

  • Add the IP/Domain to <LoginAllowedIPs></LoginPageAllowedIPs> in the Settings.xml file

For further information on Active Directory, visit the Decisions Forum.

Was this article helpful?