Tutorial: Azure Active Directory single sign-on (SSO) integration with EBSCO
In this tutorial, you'll learn how to integrate EBSCO with Azure Active Directory (Azure AD). When you integrate EBSCO with Azure AD, you can:
- Control in Azure AD who has access to EBSCO.
- Enable your users to be automatically signed-in to EBSCO 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.
- EBSCO single sign-on (SSO) enabled subscription.
In this tutorial, you configure and test Azure AD SSO in a test environment.
- EBSCO supports SP and IDP initiated SSO.
- EBSCO 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 EBSCO from the gallery
To configure the integration of EBSCO into Azure AD, you need to add EBSCO 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 EBSCO in the search box.
- Select EBSCO 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 EBSCO
Configure and test Azure AD SSO with EBSCO 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 EBSCO.
To configure and test Azure AD SSO with EBSCO, perform the following steps:
- Configure Azure AD SSO - to enable your users to use this feature.
- Configure EBSCO SSO - to configure the single sign-on settings on application side.
- Create EBSCO test user - to have a counterpart of B.Simon in EBSCO 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 EBSCO 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, if you wish to configure the application in IDP initiated mode, then perform the following step:
In the Identifier text box, type the URL:
Click Set additional URLs and perform the following step if you wish to configure the application in SP initiated mode:
In the Sign-on URL text box, type a URL using the following pattern:
http://search.ebscohost.com/login.aspx?authtype=sso&custid=<unique EBSCO customer ID>&profile=<profile ID>
The Sign-on URL value is not real. Update the value with the actual Sign-on URL. Contact EBSCO Client support team to get these values. You can also refer to the patterns shown in the Basic SAML Configuration section in the Azure portal.
o Unique elements:
o Custid = Enter unique EBSCO customer ID
o Profile = Clients can tailor the link to direct users to a specific profile (depending on what they purchase from EBSCO). They can enter a specific profile ID. The main IDs are eds (EBSCO Discovery Service) and ehost (EBSOCOhost databases). Instructions for the same are given here.
EBSCO 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.
The name attribute is mandatory and it is mapped with Name Identifier value in EBSCO application. This is added by default so you don't need to add this manually.
In addition to above, EBSCO application expects few more attributes to be passed back in SAML response which are shown below. These attributes are also pre populated but you can review them as per your requirements.
Name Source Attribute FirstName user.givenname LastName user.surname user.mail
On the Set up single sign-on with SAML page, in the SAML Signing Certificate section, find Federation Metadata XML and select Download to download the certificate and save it on your computer.
On the Set up EBSCO 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 EBSCO.
- In the Azure portal, select Enterprise Applications, and then select All applications.
- In the applications list, select EBSCO.
- 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 EBSCO SSO
To configure single sign-on on EBSCO side, you need to send the downloaded Federation Metadata XML and appropriate copied URLs from Azure portal to EBSCO support team. They set this setting to have the SAML SSO connection set properly on both sides.
Create EBSCO test user
In the case of EBSCO, user provisioning is automatic.
To provision a user account, perform the following steps:
Azure AD passes the required data to EBSCO application. EBSCO’s user provisioning can be automatic OR require a one-time form. It depends on whether the client has a lot of pre-existing EBSCOhost accounts with personal settings saved. The same can be discussed with the EBSCO support team during the implementation. Either way, the client doesn’t have to create any EBSCOhost accounts prior to testing.
You can automate EBSCO host user provisioning/personalization. Contact EBSCO support team about Just-In-Time user provisioning.
In this section, you test your Azure AD single sign-on configuration using My Apps.
When you click the EBSCO tile in My Apps, you should get automatically signed-on to your EBSCO application. For more information about My Apps, see Introduction to My Apps.
Once you login to the application, click on the sign in button in the top right corner.
You will receive a one-time prompt to pair the institutional/SAML login with an Link your existing MyEBSCOhost account to your institution account now OR Create a new MyEBSCOhost account and link it to your institution account. The account is used for personalization on the EBSCOhost application. Select the option Create a new account and you will see that the form for personalization is pre-completed with the values from the saml response as shown in the screenshot below. Click ‘Continue’ to save this selection.
After completing the above setup, clear cookies/cache and login again. You won’t have to manually sign in again and the personalization settings are remembered.
Once you configure EBSCO 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.