Skip to main content

How to set up Azure SSO

Updated over 10 months ago

The objective of this article is to demonstrate the steps to be performed in Cliquify SAML 2.0 within Azure Active Directory (Azure AD) to enable Single sign-on (SSO) in a centralized and secure way of controlling access to Cliquify Application.

Step 1: Go to your Azure Portal and sign in (Important: make sure you are in the correct directory.

Step 2: In the left navigation panel, select Azure Active Directory.

Step 3: Navigate to Enterprise applications, and then select All applications.

Step 4: To add a new application, select the New Application button at the top of the pane.

Step 5: Click Create your own application and on the right panel type the name of your custom non-gallery app and click Create button.

Step 6: Once the Application is added to your directory, navigate to the Single sign-on tab.

Step 7: Edit the Basic SAML Configuration settings and paste the following values provided by Cliquify team.

  • Paste Entity ID under Identifier (Entity ID).

  • Paste Reply URL (Assertion Consumer Service URL).

Step 8: Save and Close.

Step 9: Next, edit User Attributes & Claims.

Step 10: Under Choose name identifier format

  • Select Attribute

  • Enter user.mail (or whatever is the attribute for email address)

  • Click Save

Step 11: Copy the Login URL

Step 12: Click on Download next to Federation Metadata XML, present in the SAML Signing Certificate.

Step 13: Send the downloaded Federation Metadata XML file & Login URL back to Cliquify support team.

Step 14: Click Save Configuration.

Step 15: Test the integration via Azure Active Directory Configuration, Click Test button.

Step 16: Click Test sign in button


โ€‹

Step 17: You will be prompted towards Service Provider flow and your user be authenticated via Azure AD. You have to log in with the same email address on Cliquify.me Azure AD app before you can test and enable it.

Step 18: Upon successful test, it will enable the Single Sign-on feature for your Organization.

Did this answer your question?