Introduction
Springboard support authentication with any SAML 2.0 compliant service. This documentation has been written on the assumption that you are using Azure AD. If you are using a different authentication provider, please request the required documentation from PeopleScout.
The steps required to configure Springboard to authenticate against your Azure AD tenancy are outlined below;
Assumptions
The following documentation assumes that you have the following in place;
• Office 365 Tenancy
• Azure AD Premium (Springboard is a non-gallery Application)
• Global Administrator privileges in Azure
• Azure Active Directory Security Group to grant access to Springboard
Prerequisites
Before commencing the steps below please ensure you have;
• Provided PeopleScout with your careers site URL e.g https://careers.mycompany.com
• The Metadata.xml file (provided by PeopleScout)
Dependencies
At the completion of this document you will have;
• Set up Springboard as an Enterprise Application with Azure AD
• Configured Springboard User role within Azure AD
• Configured claim rules
• Generated a Token Signing Certificate (Exported from Azure AD)
Create Enterprise Application
- Log into your Azure AD Portal (https://aad.portal.azure.com)
- Select Enterprise Applications
- Select New Application
- Select Non-gallery application
- Give the application an easily identifiable name such as “Springboard”
- Select Add
Configure Single Sign On (SSO)
- Select Configure single sign-on (required)
- Select SAML
- Select Upload metadata file
- Select the Metadata.xml file provided to you by PeopleScout
- Confirm that the Identified (Entity ID) and Reply URL (Assertion Consumer Service URL) are correct They should match your careers site URL trailed by /sso-service-provider/
- Select Save
- Click “X” to close the Basic SAML Configuration Window
- Select the pencil to edit User Attributes & Claims
- Remove all additional claims
- Select Add new claim
- Name = RASP_ORG_ID
- Source attribute = XXXXX (Provided by PeopleScout)
- Select Save
Creating Springboard Role
- Navigate to Azure Active Directory
- Select App Registrations
- Select Springboard
- Navigate to Manifest
- Paste the following code into the manifest
{
Please note: See below to confirm the desired format. This is the result of what we want our Manifest to look like. Notice the “SpringboardUser” role. Note: msiam_access role must be left as default. Do not amend this.
"allowedMemberTypes": [
"User"
],
"description": "SpringboardUser",
"displayName": "SpringboardUser",
"id": "257203a4-9e02-42ad-bff6-fb179520dadd",
"isEnabled": true,
"origin": "Application",
"value": "SpringboardUser"
} - Select Save
Assign Springboard User Role to User or Groups
- Navigate to Azure Active Directory
- Select Enterprise Applications
- Select Springboard
- Select Users and Groups
- Select Add User
- Select the User or Group you want to use to allow Springboard Access
- Select SpringboardUser role
- Select Assign
Providing Details to PeopleScout
- Select Single Sign On
- Download Certificate (Base 64)
- Copy Login URL
- Send both Login URL and Certificate (Base 64) to your PeopleScout contact