Single Sign-On Questionnaire

Save my progress and resume later | Resume a previously saved form

Resume Later

In order to be able to resume this form later, please enter your email and choose a password.

Your Email:

A Password:

Confirm Password:

Password must contain the following:

12 Characters
1 Uppercase letter
1 Lowercase letter
1 Number
1 Special character

Please select your language.

Welcome to the EBSCO Single Sign-On (SSO) questionnaire. This questionnaire is designed for you to help us learn as much as we can about your organization’s SAML-based SSO capabilities. The answers you provide will be used by the EBSCO Support team to better facilitate the setup, testing and deployment of the SSO connection to your EBSCO resources.

The estimated time for completion of the questionnaire is 5-7 minutes. In order to complete, you should have a working proficiency of your organization’s SSO capabilities and be able to upload or provide a link to the IdP SAML metadata file. If you are unsure or unable to complete the questionnaire, please contact your Implementation Project Manager (IPM) or email us at eds@ebsco.com, and we’ll be glad to assist you.

Please provide your contact information. We will contact you to acknowledge the review of your submitted questionnaire and indicate setup status.

First Name

Last Name

Phone Number

EBSCO ID

Organization Name

Are you utilizing your EBSCO products in different groups within EBSCOadmin?

YesNo

Are you an OpenAthens customer or utilizing OpenAthens in any fashion?

YesNo

What SAML/SSO system will your institution use to connect to EBSCO?

Our federation. Click here to view a list of Shibboleth federations Our SAML Identity Provider e.g. Okta, PingFederate, OneLogin, ADFS, Azure etc.Google Workspace

Please specify your Federation:

Please specify your SAML Identity Provider:

Please specify which platform your organization uses for managing SAML-based SSO connections.

Please provide the SAML metadata file from your organization’s IdP using one of the methods provided below. This file is required in order to create your SSO configuration in EBSCO.

I will upload the file in this formI will provide you a URL to the data file

Please upload your file here. Note the maximum file size is 20 MB.

Please paste the URL below.

Do you want to use the default settings for Google Workspace (primary email address as Persistent ID)?

YesNoPersistent ID is a required attribute for EBSCO’s SSO integration.

Please enter the settings you would like to use:

Do you want to use Personalization to automatically log users into their personal EBSCO folders?

YesNoPlease note that if your organization does not send the optional personal attributes (first name, last name, email) in the assertion, end users will need to enter these detail themselves (only once) when they first personalize in EBSCO, and we will securely store all user data.

For more information, please visit the following support document: Set up your own custom SAML application and view an example of Attribute Mapping

First Name

Last Name

Primary Email

For more information, please visit the following support document: Set up your own custom SAML application

Attach your Google metadata (download it from the Google Identity Provider details page):

Please indicate the Attribute Names & Entitlements that your organization will be including in your SAML Assertions.

Note: Persistent ID is a required attribute for EBSCO’s SSO integration. We require the attribute name (outgoing claim) as it will appear in a SAMLResponse Attribute Statement. Please indicate exactly how the Attribute Name will be released to EBSCO. Examples of the Attribute Names we’re looking for below can be found here and here.

Persistent ID

Email Address

First Name

Last Name

Entitlement (Optional)

Affiliation (Optional)

Please indicate the Attribute Names & Entitlements released by your federation

Note: Persistent ID is a required attribute for EBSCO’s SSO integration. Most Shibboleth federations release TargetedID as their anonymous persistent user ID (see below). We'll use this as your Persistent ID unless you provide an alternative e.g. eduPersonPrincipalName (eppn). Consult your federation if you're unsure what attribute(s) are released to EBSCO.

Persistent ID

Most federations recommend TargetedID (attribute name: urn:oid:1.3.6.1.4.1.5923.1.1.1.10).

Email Address

First Name

Last Name

Please list any required scoped affiliation(s) and/or entitlement value(s) e.g. member@uni.com, staff@uni.com, student@uni.com etc

Affiliation (Optional)

We use attribute name "urn:oid:1.3.6.1.4.1.5923.1.1.1.9" for Scoped Affiliation.

Entitlement (Optional)

We use attribute name "urn:oid:1.3.6.1.4.1.5923.1.1.1.7" for Entitlement.

Personalization preferences - MyEBSCO user account(s)

SSO can authenticate and personalize access on EBSCO websites.

We use attributes (see previous page) to create MyEBSCO personal accounts. MyEBSCO personalizes the research experience e.g. saving items, creating alerts, creating research projects etc. A MyEBSCO account isn't required to access EBSCO content. However, it is required to use personal features.

EBSCO retains user information to create and maintain these accounts. It's important your users know how we use their information. EBSCO displays a one-time privacy consent form before we create accounts. The form displays the first time SSO users log in (if immediate personalization is enabled). Alternatively, we can delay the form until the user needs a MyEBSCO account. Read more about personalization options. Users can opt out OR delete their account at any time. Read more about GDPR.

Consider your preferences and privacy policy. Ask your IPM if you need more information.

How should we personalize access for SSO users?

Immediate (recommended) - personalize access when users log in Delayed - personalize access when MyEBSCO is needed Forced - require personalization to access EBSCO content (display form on login, users see error if they opt out)No personalization - authenticate access but do not personalize access using SSO (users can register for a separate MyEBSCO account)

Please indicate which connection methodology your organization will use to provide access to the EBSCO resources.

IdP-initiated connection onlySP-initiated connection onlyBoth

Note: Only SP-initiated connections enable full support for EBSCO’s persistent links and institutional login page(s)

Please provide your IdP-initiated link prefix/syntax

It is recommended that a Test User Account for your SSO service is provided to help our EBSCO SSO Support team test and verify the connection.

The Test User Account must be configured with the same user data attributes to be used for production users. Having a test account available to the EBSCO team can greatly decrease the turnaround time of a new SSO setup and can also be extremely helpful in troubleshooting any issues we may come across during the setup process.

Can you provide us with test credentials?

YesNo

Thank you!

A member of our team will reach out soon to securely obtain test credentials. Please proceed to the next page.

Do you have a contact that will commit to running verification tests when needed?

YesNo

Contact information who can commit to running verification testing

IF THERE ISN'T ANYONE WHO CAN COMMIT TO RUN VERIFICATION TESTING WITH US WE WILL HAVE TO HOLD YOUR IMPLEMENTATION UNTIL SOMEONE CAN BE AVAILABLE OR UNTIL YOU CAN PROVIDE TEST CREDENTIALS.

Will all users who have access to the EBSCO products be bound by SSO authentication?

Yes, everyone will use SSONo, not everyone will use SSO

Please explain groups that would not access through SSO

Please specify any additional questions, comments, customizations, requirements, etc. in the box below regarding your SSO implementation.

Please list any additional contacts for this questionnaire using the below.

Additional contact email:

Save my progress and resume later | Resume a previously saved form