This article describes how to create a Fortanix Application in Azure Active Directory for SAML authentication.
Configuring Single Sign-On (SSO) to use Microsoft Azure Active Directory (AD) as a Security Assertion Markup Language Identity Provider (SAML IdP) requires Active Directory Premium. You must sign in to Fortanix Data Security Manager (DSM) as an Administrator and to the Azure portal using your Azure Active Directory administrator account. This process requires you to create a non-gallery application in Azure.
For a more detailed explanation on configuring SAML in Azure AD, see the Microsoft documentation:
Configure single sign-on to applications that are not in the Azure Active Directory application gallery.
Creating a Fortanix Application in Azure AD
Sign in to Fortanix UI as an administrator, and in a separate window, sign in to Azure Active Directory as an an administrator. To create a Fortanix application, follow the steps below:
Navigate to Azure Active Directory > Enterprise applications.
Figure 1: Navigate to Enterprise applications
Click New application.
Figure 2: Click New Applications
Click Create your own application.
This opens the Create your own application pane.
Figure 3: Click Create your own application
Enter a name for your new app.
Ensure Integrate any other application you don’t find in the gallery is selected.
When the application's Overview page displays, the application is created.
Click Users and groups.
Figure 4: Click Users and groups
Click +Add user/group. Highlight your choice in the search bar, click Select, and then click Assign.
Repeat as necessary to add users/groups.
Click Single sign-on.
Select the SAML tile.
This opens the Set up Single Sign-On with SAML page.
Figure 5: Select the SAML tile
In Section 1, provide the two values listed below. You can copy both values from the Lacework Console authentication settings.
Identifier (Entity ID):
Copy from Service Provider Entity ID
Reply URL (Assertion Consumer Service URL):
Copy from Assertion Consumer Service URL
In Section 2, ensure that you have the correct Unique User Identifier specified under Attributes and Claims. The default user identifier is preconfigured as
user.userprincipalname. However, depending on your organization, you can also use the email address as the Unique User Identifier by specifying
In Section 3, download and save the Federation Metadata XML file.
Figure 6: Provide the required details and download and save the Federation Metadata XML file