Tutorial: Integrate NEOGOV with Azure Active Directory
In this tutorial, you'll learn how to integrate NEOGOV with Azure Active Directory (Azure AD). When you integrate NEOGOV with Azure AD, you can:
- Control in Azure AD who has access to NEOGOV.
- Enable your users to be automatically signed-in to NEOGOV with their Azure AD accounts.
- Manage your accounts in one central location - the Azure portal.
To learn more about SaaS app integration with Azure AD, see What is application access and single sign-on with Azure Active Directory.
To get started, you need the following items:
- An Azure AD subscription. If you don't have a subscription, you can get one-month free trial here.
- NEOGOV single sign-on (SSO) enabled subscription.
In this tutorial, you configure and test Azure AD SSO in a test environment. NEOGOV supports IDP initiated SSO.
Adding NEOGOV from the gallery
To configure the integration of NEOGOV into Azure AD, you need to add NEOGOV 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 NEOGOV in the search box.
- Select NEOGOV from results panel and then add the app. Wait a few seconds while the app is added to your tenant.
Configure and test Azure AD single sign-on
Configure and test Azure AD SSO with NEOGOV 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 NEOGOV.
To configure and test Azure AD SSO with NEOGOV, complete the following building blocks:
- Configure Azure AD SSO - to enable your users to use this feature.
- Configure NEOGOV SSO - to configure the Single Sign-On settings on application side.
- Create an Azure AD test user - to test Azure AD single sign-on with B. Simon.
- Assign the Azure AD test user - to enable B. Simon to use Azure AD single sign-on.
- Create NEOGOV test user - to have a counterpart of B. Simon in NEOGOV 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 NEOGOV 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 page, enter the values for the following fields:
a. In the Identifier text box, type a URL using the following pattern:
Environment URL pattern Production
b. In the Reply URL text box, type a URL using the following pattern:
Environment URL pattern Production
NEOGOV 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. NEOGOV application expects nameidentifier to be mapped with user.objectid, so you need to edit the attribute mapping by clicking on Edit icon and change the attribute mapping.
In addition to above, NEOGOV application expects few more attributes to be passed back in SAML response. In the User Claims section on the User Attributes dialog, perform the following steps to add SAML token attribute as shown in the below table:
Name Source Attribute user.mail
a. Click Add new claim to open the Manage user claims dialog.
b. In the Name textbox, type the attribute name shown for that row.
c. Leave the Namespace blank.
d. Select Source as Attribute.
e. From the Source attribute list, type the attribute value shown for that row.
f. Click Ok
g. Click Save.
On the Set up Single Sign-On with SAML page, In the SAML Signing Certificate section, click copy button to copy App Federation Metadata Url and save it on your computer.
Configure NEOGOV SSO
To configure single sign-on on NEOGOV side, you need to send the App Federation Metadata Url to NEOGOV support team. They set this setting to have the SAML SSO connection set properly on both sides.
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 NEOGOV.
In the Azure portal, select Enterprise Applications, and then select All applications.
In the applications list, select NEOGOV.
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're expecting any role value in the SAML assertion, in the Select Role dialog, select the appropriate role for the user from the list and then click the Select button at the bottom of the screen.
In the Add Assignment dialog, click the Assign button.
Create NEOGOV test user
In this section, you create a user called B. Simon in NEOGOV. Work with NEOGOV support team to add the users in the NEOGOV platform. Users must be created and activated before you use single sign-on.
When you select the NEOGOV tile in the Access Panel, you should be automatically signed in to the NEOGOV for which you set up SSO. For more information about the Access Panel, see Introduction to the Access Panel.
Send feedback about: