In this part of the workflow, you are creating the application tile that SSO users will click to access the Alida platform.

1. Log in to the Azure Portal.
2. Under Azure services, click Enterprise applications.
3. Click New application.
   
4. Click Create your own application.
5. Enter a name for the application, which will be the label on the SSO tile (for example, Alida).
6. Select the option Integrate any other application you don't find in the gallery (Non-gallery).
7. Click Create.

After you create the application tile, you need to copy specific configuration values. You'll enter these values into Alida's SSO Setup page later.

1. Click Manage > Single sign-on.
2. Select SAML as the single sign-on method (if not previously selected).
3. Copy the Microsoft Entra Identifier and store the value for later use.
4. Click Certificate (Base64) > Download, open the .cer file in Notepad, and store the X.509 certificate for later use.

   Click the screenshot below to view a larger version.

   

Enter the Azure configuration values into Alida's SSO Setup page.

1. Sign in to the Alida platform and switch to the desired community.
2. Ensure that there's a user who matches the email of a potential SSO user (for example, bob.smith@example.com).

   This user must be part of the domain you added. This user must also be a user in the Alida community.

   For more information about adding new users to a community, see Add a user.

3. Open Product Settings > SSO > Setup.
4. In the Identity Provider drop-down list, select Azure.
5. Under Microsoft Entra Identifier, enter the Microsoft Entra Identifier you stored earlier.
6. Under X.509 Certificate, enter the X.509 certificate you stored earlier.
7. Under Email claim, enter http://schemas.xmlsoap.org/ws/2005/05/identity/claims/email
8. Click Save.
9. Copy the Single Sign-On URL and store it for later use.
10. Copy the Audience Entity ID and store it for later use.

    Click the screenshot below to view a larger version.

    

Add the registered domain that your company owns and that you use for employees' email addresses.

1. Open Product Settings > SSO.
2. Click the Domains tab.
3. In the Add new domain field, type the domain value, select the Type (CNAME or TXT), and click Add Domain.

   For example, if a potential SSO user's email is bob.smith@example.com, you'd type example.com as the domain.

   The new entry is added to the domains list as an Unverified domain.

4. Click the down-arrow to the left of the domain entry to display the DNS Record.
   
5. Keep the browser tab that has the Alida Domains page open. Open a new browser tab to access your DNS site.
6. Add the values from the Domains page to your DNS configuration.

   For both CNAME and TXT DNS records, the three required values are listed separated by spaces:

   • Add the first value as the owner or source name.
   • Add the second value as the DNS record type. It will either be CNAME or TXT.
   • Add the third value as the target or destination name.

   Example
   This example shows the two supported DNS record formats configured in AWS Route 53. The first is a TXT record, and the second is a CNAME record. The first value in the DNS record is added as the Record Name field. The second value in the DNS record is added as the Type field. The third value in the DNS record is added as the Value/Route traffic to field.

7. On the Alida Domains page, select Verify from the domain's action menu.

   The domain's status changes to Verified.

8. Click Apply.
   The domain status changes from Verified to Active.

   

1. Log in to the Azure Portal.
2. Under Azure services, click Enterprise applications and open your application (for example, Alida).
3. Click Manage > Single sign-on.
4. Click Basic SAML Configuration > Edit.
5. Under Identifier (Entity ID), enter the Audience Entity ID you stored earlier.
6. Under Reply URL (Assertion Consumer Service URL), enter the Single Sign-On URL you stored earlier.
   
7. Click Save.
8. Click Attributes & Claims > Edit.
9. Delete all existing Additional claims.
10. Click Add new claim and create a new claim:
    • Name: email
    • Namespace: http://schemas.xmlsoap.org/ws/2005/05/identity/claims
    • Source: Attribute
    • Source attribute: user.mail

    

In order for SSO to work, the same user must exist in Azure (with the Alida application associated to that user) and in the Alida platform.

1. Log in to the Azure Portal.
2. Under Azure services, click Enterprise applications and open your application (for example, Alida).
3. Click Manage > Users and groups.
4. Click Add user/group.
5. Click Users and groups > None Selected.
6. Select the user you added in the panel (for example, bob.smith@example.com) and click Select.

   Click the screenshot below to view a larger version.

   
7. Click Select a role > None Selected.
8. Click User, then click Select.
9. Click Assign.

1. Ask the user you added (for example, bob.smith@example.com) to log in to MyApps using their credentials.
2. The user clicks the application's tile (for example, Alida).
   
   Result: The community opens or they are able to switch to it.