Tutorial: Azure AD SSO integration with Fidelity NetBenefits
In this tutorial, you'll learn how to integrate Fidelity NetBenefits with Azure Active Directory (Azure AD). When you integrate Fidelity NetBenefits with Azure AD, you can:
- Control in Azure AD who has access to Fidelity NetBenefits.
- Enable your users to be automatically signed-in to Fidelity NetBenefits 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.
- Fidelity NetBenefits single sign-on (SSO) enabled subscription.
In this tutorial, you configure and test Azure AD single sign-on in a test environment.
Fidelity NetBenefits supports IDP initiated SSO.
Fidelity NetBenefits supports Just In Time user provisioning.
Identifier of this application is a fixed string value so only one instance can be configured in one tenant.
Add Fidelity NetBenefits from the gallery
To configure the integration of Fidelity NetBenefits into Azure AD, you need to add Fidelity NetBenefits 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 Fidelity NetBenefits in the search box.
- Select Fidelity NetBenefits 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 Fidelity NetBenefits
Configure and test Azure AD SSO with Fidelity NetBenefits 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 Fidelity NetBenefits.
To configure and test Azure AD SSO with Fidelity NetBenefits, perform the following steps:
- Configure Azure AD SSO - to enable your users to use this feature.
- 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.
- Configure Fidelity NetBenefits SSO - to configure the single sign-on settings on application side.
- Create Fidelity NetBenefits test user - to have a counterpart of B.Simon in Fidelity NetBenefits 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 Fidelity NetBenefits 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 pencil icon for Basic SAML Configuration to edit the settings.
On the Basic SAML Configuration section, perform the following steps:
a. In the Identifier text box, type one of the following values:
For Testing Environment:
For Production Environment:
b. In the Reply URL text box, type a URL that to be provided by Fidelity at time of implementation or contact your assigned Fidelity Client Service Manager.
Fidelity NetBenefits 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. Fidelity NetBenefits application expects nameidentifier to be mapped with employeeid 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.
Fidelity NetBenefits support Static and Dynamic Federation. Static means it will not use SAML based just in time user provisioning and Dynamic means it supports just in time user provisioning. For using JIT based provisioning customers have to add some more claims in Azure AD like user's birthdate etc. These details are provided by the your assigned Fidelity Client Service Manager and they have to enable this dynamic federation for your instance.
On the Set up Single Sign-On with SAML page, in the SAML Signing Certificate section, click Download to download the Federation Metadata XML from the given options as per your requirement and save it on your computer.
On the Set up Fidelity NetBenefits section, copy the appropriate URL(s) as per 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 firstname.lastname@example.org. 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 Fidelity NetBenefits.
- In the Azure portal, select Enterprise Applications, and then select All applications.
- In the applications list, select Fidelity NetBenefits.
- 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 Fidelity NetBenefits SSO
To configure single sign-on on Fidelity NetBenefits side, you need to send the downloaded Federation Metadata XML and appropriate copied URLs from Azure portal to Fidelity NetBenefits support team. They set this setting to have the SAML SSO connection set properly on both sides.
Create Fidelity NetBenefits test user
In this section, you create a user called Britta Simon in Fidelity NetBenefits. If you are creating Static federation, please work with your assigned Fidelity Client Service Manager to create users in Fidelity NetBenefits platform. These users must be created and activated before you use single sign-on.
For Dynamic Federation, users are created using Just In Time user provisioning. For using JIT based provisioning customers have to add some more claims in Azure AD like user's birthdate etc. These details are provided by the your assigned Fidelity Client Service Manager and they have to enable this dynamic federation for your instance.
In this section, you test your Azure AD single sign-on configuration with following options.
Click on Test this application in Azure portal and you should be automatically signed in to the Fidelity NetBenefits for which you set up the SSO.
You can use Microsoft My Apps. When you click the Fidelity NetBenefits tile in the My Apps, you should be automatically signed in to the Fidelity NetBenefits for which you set up the SSO. For more information about the My Apps, see Introduction to the My Apps.
Once you configure Fidelity NetBenefits 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.
Submit and view feedback for