Comment on page
Setup SSO for ImageKit on Azure
There are two main steps required to set up SSO using Azure on ImageKit:
Azure subscription Although you may use a free account on Azure to set up and test the SSO application, having a premium Azure subscription is recommended for seamless role provisioning for your users. Read more here.
First, you need to create an application on Azure Active Directory and generate a Federation Metadata XML file.
- 2.Navigate to the "Enterprise applications" screen using the side navigation menu
- 3.Click the "New application" button, then click on "Create your own application"
- 4.In the form that opens up, choose the "Non-gallery application" radio button as shown below.
- 5.Input a name for the application, we will use "ImageKit" for this guide.
Click "Create" and wait until you are redirected to the application page.
Create a non-gallery application
On the application page, navigate to the 'Single sign-on' screen. Select "SAML" as the single sign-on method.
Single sign-on method
On the next screen, we will configure various authentication URLs as shown:
Basic SAML configuration
Now you need to specify four keys that ImageKit uses to authorize and provision your users:
For the purpose of this guide, we will map "imagekit_role" to
user.departmentAzure key. Ensure that this field is populated correctly in your Azure user object while testing the app.
Attributes and claims
Save the list of attributes and claims to finish this step.
Download the Federation Metadata XML file and keep it in a safe location. You will need to upload this XML file to your ImageKit account in a later step.
Download Federation Metadata XML
Enable SSO for all users
If you have administrator privileges on your ImageKit account, you can enable SSO for all the users in your account as follows:
Your users should now be able to use Microsoft Azure SSO to log into ImageKit. You can verify this by clicking the 'Test' button on the 'Single sign-on' set up screen on Azure.
ImageKit SSO login screen
You can disable SSO login for the users on your ImageKit account by deleting the Metadata XML.
Azure Active Directory requires the Identifier or EntityID to be unique across the organization's applications.
However, you may want to create multiple unique instances of SSO application for use with ImageKit within a single Azure Active Directory instance – for example, if you have an agency account that manages SSO for multiple child accounts within your own company organization.
To do this, you can attach a hash suffix with the unique
imagekit_idto the Identifier (EntityID) and Reply URL of each such child account.
The SAML configuration of each such app then becomes similar to the following, where
child_imagekit_idis the unique
imagekit_idof that child account:
To ensure that the login flow initiated from ImageKit works smoothly, save the new unique Identifier URL in the Entity ID field on the ImageKit dashboard SSO settings page of the child account.
If the Entity ID field value is removed, then the account will revert to following the default value of Identifier and Reply URL when SSO login is initiated from ImageKit, i.e.
Configure Entity ID