Training Platform SCIM Walkthrough

To make use of user provisioning via SCIM you must have SSO support enabled and SCIM
support enabled by a Living Security customer support representative.
Once these features of your account are enabled you can proceed to the configuration page to
enable SCIM and generate your required API key.

Until SCIM connection is complete, you must continue to use CSV file upload to provision SSO access.

Downloadable PDF User Provisioning (SCIM) Walkthrough



Enable SCIM by interacting with the toggle under User Provisioning 

If SCIM has not been enabled by a Living Security representative then the toggle will not appear
for you and you will need to contact Living Security

 

After enabling the toggle, save your configuration

Now you will see the API URL you will need for your SCIM client and the ability to generate an
API key which will also be used within your SCIM client

Press “Create API key” then give your API key a name (What you name it is entirely up to you)

At this point, you should see an API key secret displayed and a dialog asking you to store your
key in a safe place as it will only be displayed here once

If you lose the API key you can always generate a new one, but you will need to add it to your
SCIM client.
At this point, you have successfully configured your Living Security Training Platform to enable
your SCIM client to connect. Next you will need to take the API key you generated and the API
URL to your SCIM client for configuration.
SCIM CLIENT CONFIGURATION
Your SCIM client will require the API url you received in the previous steps to configure your
Living Security Platform

Supported Actions:

The Living Security SCIM API supports SCIM 2.0 and the following actions:
● Importing new users and profile updates
● Pushing new users
● Pushing profile updates
The Living Security SCIM API does not support groups


Authentication:

The Living Security SCIM API supports Authentication via HTTP Header ( Authorization)
In the form:
Header: Authorization
Value: Bearer ***************
Where the value following bearer is your API Key


Unique Identifier Field for Users:

The unique identifier field for users within the Living Security API is userName


Example:
Here is an example of a fully configured SCIM client within Okta. 

Detailed instructions for establishing SCIM in Okta

Detailed instructions for establishing SCIM in Azure Active Directory

Attributes Supported by the Living Security SCIM API

SCIM Attribute

Application Label

Notes

Available on “User Management : User List” Page

Available on “Audience” Page Table

Available on “Audience” Page Filters

Used by Campaign Builder Notifications

Used by Next Generation Reporting Filtering

name : familyName

Last Name

 

Yes

Yes

 

Yes

 

name : givenName

First Name

 

Yes

Yes

 

Yes

 

title

Title

 

Yes

Yes

Yes

 

Yes

userType

User Type

 

Yes

Yes

Yes

 

Yes

timezone

Time Zone

 

Yes

Yes

Yes

 

Yes

emails

Email Address

Import the first email address

Yes

Yes

 

Yes

 

ims

Instant Message

 

 

 

 

Yes

 

addresses

<none>

Import the first address

 

 

 

 

 

addresses : locality

City

 

Yes

Yes

Yes

 

Yes

addresses : region

State

 

Yes

Yes

Yes

 

Yes

addresses : country

Country

 

Yes

Yes

Yes

 

Yes

roles

Company Roles

 

Yes

Yes

Yes

 

Yes

organization

Organization

 

Yes

Yes

Yes

 

Yes

division

Division

 

Yes

Yes

Yes

 

Yes

department

Department

 

Yes

Yes

Yes

 

Yes

manager : displayName

Manager Name

 

Yes

Yes

Yes

Yes

 

manager : $ref

<none>

Required if Manager Name is selected for import

 

 

 

Yes

 

The attributes below are mandatory.

 

SCIM Attribute

Application Label

Notes

Available on “User Management : User List” Page

Available on “Audience” Page

Used by Campaign Builder Notifications

active

Company’s User Activity

This is independent of the Platform-internal “Status” field.

Yes

 

 

userName