This article will walk you through configuring user provisioning via SCIM if you are using Entra ID.
Before you Start
Speak to your Customer Success Manager (CSM) and Account Manager (AM) about your options and the costs around setting up user provisioning via SCIM.
You may also want to discuss details such as what user domains you want to be able to use SSO and whether your CSM will be helping your set this or ensuring you have the correct permissions access to set yourself up.
Getting started on the Skillcast Application
First, you need to prepare credentials and attributes.
Create a token
Go to Management Console > Configuration> API Managementment
Create a new user: Username: e.g. 'SCIM API', add the user domain in 'Domain access' and Tick the following options: 'Enable SCIM v2 API' under the API heading. 'Manage Audience Groups' 'Manage Users' 'Reporting'. Click 'Add API user'.
Click 'Generate new session ID' to generate a token to be used later.
Adding attributes
Ensure that you have added all additional attributes you want to populate on the skillcast portal. You will have to ensure that you make note of all the attributes names on the Skillcast portal as you will need this later when setting up your attributes in Entra ID.
Connecting your Entra ID environment to your Skillcast Application
Entra ID custom Enterprise app
Go to Azure Active Directory > Enterprise applications
Choose
+ New application
Choose
+ Create your own application
Enter an app name and choose
Integrate any other application you don't find in the gallery (Non-gallery)
. Then clickCreate
.
Under the heading
manage
, chooseProvisioning
, thenGet started
Provisioning setup
For
Provisioning Mode
selectAutomatic
Enter the credentials:
Tenant URL:
https://[clientid].skillcast.io/skillcastApi/scim
Your client ID can be found in your Skillcast application URL which will look something like https://mycompany.e-learningportal.com/, the bold part of the URL is your client ID.Secret Token this is the session ID you generated on the Skillcast app. You can find
Session Details
from the API management area of the portal. i.e.BDDDBB7A-CD39-431F-8B52EC014F4E895C
Click
Test Connection
. Azure should return the message
The supplied credentials are authorised to enable provisioning
Click
Save
. Click the top rightX
to close.Choose
Edit provisioning
. A new section will be available calledMappings
. Expand this section.Click
Provision Azure Active Directory Groups
Change
Enabled
toNo
. ClickSave
. ClickYes
forSave changes
. Then clickProvisioning
in the top breadcrumb.
Attribute setup
Click
Provision Azure Active Directory Users
.At the bottom of the page click
Show advanced options
Click
Edit attribute list for customappsso
Scroll to the bottom of the attribute list. Create a new attribute for each Skillcast attribute that you wish to update.
Click
save
and underAre you sure you want to make these changes
, chooseyes
. Click the top rightX
to close.Again, click
Click
Provision Azure Active Directory Usersand at the bottom of the table, click
Add New Mapping`Using the previous details, add a new attribute
Click
ok
When finished, click
save
A confirmation message may display, clickYes
.
User matching (optional)
You may want to match users on their email address instead of the Entra ID default of username
.
Choose the field you wish to match users on. i.e. mail
For
Match objects using this attribute
chooseYes
. PressOk
Choose the attribute with a
Matching precedence
of1
For
Match objects using this attribute
chooseNo
. PressOk
Edit the field from step 1, change the
Matching precedence
to1
. PressOk
Click
Save
A confirmation message may display, clickYes
.
Add users to Enterprise application
Within the Enterprise Application, choose
User and groups
Click
Add user/group
Depending on your Active Directory level, choose
None Selected
underUsers
Select the relevant users in the popup, click
Select
, clickAssign
Test with Provision on demand
Within the Enterprise Application, choose
Provisioning
Click
Provision on demand
Select a user, click
Provision
Limitations and Considerations
Provisioning via SCIM can only be enabled with one token linked to one domain. You will be unable to provision users into different domains using the same credentials/token.
If you are using a different app to set up provisioning via SCIM the steps on the Skillcast platform will be the same; you should have similar steps on the other application however, you will need to seek guidance from that third party for exact details.