To set up SSO for technician login with Azure AD and SuperOps.ai please follow the below steps.

1. Login to your Azure AD instance.

2. Choose Enterprise application option from the navigation menu on the left.

c8.png

3. Click on '+ New Application'.

c9.png

4. Since we are yet to be listed in AD's marketplace, Click " + Create your own application".

c10.png

5. Give it a name and choose the option, " Integrate any other application you don't find in the gallery (Non-gallery)".

c11.png

6. Here Assign users who must have access to SuperOps.ai.

c12.png

7. Now choose, "Set up single sign on" and choose SAML.

c13.png

8. Edit the Basic SAML configuration as shown below and click save:

-> Identifier ( Entity ID ) : https://superops.ai ( Mark it as default and delete any other default available)

-> Reply URL : This is the URL present under Settings -> Technician Login -> SSO -> Consumer service URL ( From your SuperOps.ai instance )

c14.png

9. Next edit user attributes to pass the below values which are essentially for SuperOps.ai to allow the login requests coming in from Azure AD.

Click edit -> Add new claim, and add the below records ( Given as name - source attribute pair)

-> email - user.mail

-> firstname - {placeholder used for first name in your instance}

-> lastname - {placeholder used for first name in your instance}

c15.png

c16.png

Please keep in mind that these attributes are case-sensitive. You'll encounter issues unless the attributes are used exactly as mentioned.

10. To add the certificate under SuperOps.ai, download the Base64 certificate available under section "3. SAML Signing Certificate" and open it in notepad. Copy the certificate and paste it in SuperOps.ai under Settings -> Technician Login -> SSO -> Certificate.

11. Similarly from Section 4, copy the login URL and paste it under login URL in SuperOps.ai. ( under Settings -> Technician Login -> SSO -> Login URL ).

📝 Note:
We do not support log out URL with Azure AD yet and this should be available soon.

12. You are all set!

Did this answer your question?