Tutorial: Azure Active Directory single sign-on (SSO) integration with NetDocuments
In this tutorial, you'll learn how to integrate NetDocuments with Azure Active Directory (Azure AD). When you integrate NetDocuments with Azure AD, you can:
- Control in Azure AD who has access to NetDocuments.
- Enable your users to be automatically signed-in to NetDocuments with their Azure AD accounts.
- Manage your accounts in one central location - the Azure portal.
To get started, you need the following items:
- An Azure AD subscription. If you don't have a subscription, you can get a free account.
- NetDocuments single sign-on (SSO) enabled subscription.
In this tutorial, you configure and test Azure AD SSO in a test environment.
- NetDocuments supports SP initiated SSO
Adding NetDocuments from the gallery
To configure the integration of NetDocuments into Azure AD, you need to add NetDocuments from the gallery to your list of managed SaaS apps.
- Sign in to the Azure portal using either a work or school account, or a personal Microsoft account.
- On the left navigation pane, select the Azure Active Directory service.
- Navigate to Enterprise Applications and then select All Applications.
- To add new application, select New application.
- In the Add from the gallery section, type NetDocuments in the search box.
- Select NetDocuments from results panel and then add the app. Wait a few seconds while the app is added to your tenant.
Alternatively, you can also use the Enterprise App Configuration Wizard. In this wizard, you can add an application to your tenant, add users/groups to the app, assign roles, as well as walk through the SSO configuration as well. Learn more about Microsoft 365 wizards.
Configure and test Azure AD SSO for NetDocuments
Configure and test Azure AD SSO with NetDocuments using a test user called B.Simon. For SSO to work, you need to establish a link relationship between an Azure AD user and the related user in NetDocuments.
To configure and test Azure AD SSO with NetDocuments, complete the following building blocks:
- Configure Azure AD SSO - to enable your users to use this feature.
- Configure NetDocuments SSO - to configure the single sign-on settings on application side.
- Create NetDocuments test user - to have a counterpart of B.Simon in NetDocuments that is linked to the Azure AD representation of user.
- Test SSO - to verify whether the configuration works.
Configure Azure AD SSO
Follow these steps to enable Azure AD SSO in the Azure portal.
In the Azure portal, on the NetDocuments application integration page, find the Manage section and select single sign-on.
On the Select a single sign-on method page, select SAML.
On the Set up single sign-on with SAML page, click the edit/pen icon for Basic SAML Configuration to edit the settings.
On the Basic SAML Configuration section, enter the values for the following fields:
a. In the Sign on URL text box, type one of the following URL patterns:
Sign on URL
b. In the Identifier (Entity ID) text box, type one of the URLs:
c. In the Reply URL text box, type one of the following URL patterns:
These values are not real. Update these values with the actual Sign on URL and Reply URL. Repository ID is a value starting with CA- followed by 8 character code associated with your NetDocuments Repository. You can check the NetDocuments Federated Identity support document for more information. Alternatively you can contact NetDocuments Client support team to get these values if you have difficulties configuring using the above information . You can also refer to the patterns shown in the Basic SAML Configuration section in the Azure portal.
NetDocuments application expects the SAML assertions in a specific format, which requires you to add custom attribute mappings to your SAML token attributes configuration. The following screenshot shows the list of default attributes, where as nameidentifier is mapped with user.userprincipalname. NetDocuments application expects nameidentifier to be mapped with ObjectID or any other claim which is applicable to your Organization as nameidentifier, so you need to edit the attribute mapping by clicking on Edit icon and change the attribute mapping.
On the Set up single sign-on with SAML page, in the SAML Signing Certificate section, find App Federation Metadata URL and copy the URL.
On the Set up NetDocuments section, copy the appropriate URL(s) based on your requirement.
Create an Azure AD test user
In this section, you'll create a test user in the Azure portal called B.Simon.
- From the left pane in the Azure portal, select Azure Active Directory, select Users, and then select All users.
- Select New user at the top of the screen.
- In the User properties, follow these steps:
- In the Name field, enter
- In the User name field, enter the email@example.com. For example,
- Select the Show password check box, and then write down the value that's displayed in the Password box.
- Click Create.
- In the Name field, enter
Assign the Azure AD test user
In this section, you'll enable B.Simon to use Azure single sign-on by granting access to NetDocuments.
- In the Azure portal, select Enterprise Applications, and then select All applications.
- In the applications list, select NetDocuments.
- In the app's overview page, find the Manage section and select Users and groups.
- Select Add user, then select Users and groups in the Add Assignment dialog.
- In the Users and groups dialog, select B.Simon from the Users list, then click the Select button at the bottom of the screen.
- If you are expecting a role to be assigned to the users, you can select it from the Select a role dropdown. If no role has been set up for this app, you see "Default Access" role selected.
- In the Add Assignment dialog, click the Assign button.
Configure NetDocuments SSO
In a different web browser window, sign into your NetDocuments company site as an administrator.
In the upper-right corner, select your name > Admin.
Select Security Center.
Select Advanced Authentication.
On the Federated ID tab, perform the following steps:
For Federated identity server type, select as Windows Azure Active Directory.
Select Choose File, to upload the downloaded metadata file which you have downloaded from Azure portal.
Create NetDocuments test user
To enable Azure AD users to sign in to NetDocuments, they must be provisioned into NetDocuments. In the case of NetDocuments, provisioning is a manual task.
To provision a user account, perform the following steps:
Sign on to your NetDocuments company site as an administrator.
In the upper-right corner, select your name > Admin.
Select Users and groups.
In the Email Address textbox, type the email address of a valid Azure Active Directory account you want to provision, and then click Add User.
The Azure Active Directory account holder will get an email that includes a link to confirm the account before it becomes active. You can use any other NetDocuments user account creation tools or APIs provided by NetDocuments to provision Azure Active Directory user accounts.
In this section, you test your Azure AD single sign-on configuration with following options.
Click on Test this application in Azure portal. This will redirect to NetDocuments Sign-on URL where you can initiate the login flow.
Go to NetDocuments Sign-on URL directly and initiate the login flow from there.
You can use Microsoft My Apps. When you click the NetDocuments tile in the My Apps, you should be automatically signed in to the NetDocuments for which you set up the SSO. For more information about the My Apps, see Introduction to the My Apps.
Once you configure NetDocuments you can enforce session control, which protects exfiltration and infiltration of your organization’s sensitive data in real time. Session control extends from Conditional Access. Learn how to enforce session control with Microsoft Defender for Cloud Apps.