Skip to main content

How to Configure Skillcast with Okta SAML SSO and SCIM Provisioning

Updated over a week ago

This guide helps you set up the Skillcast integration in Okta so your users can sign in using SAML Single Sign-On (SSO). If your project includes SCIM provisioning, you will also learn how to enable automated user management. Following these steps ensures a smooth, secure login experience for your organisation.

Before you begin, make sure you have the correct admin access and the required information from your Skillcast Customer Success Manager (CSM).

Prerequisites

Before beginning the configuration:

  • Ensure your Skillcast environment is live and SSO is included in your project scope.

  • Your Skillcast Customer Success Manager (CSM) must provide your Client ID and, if applicable, a SCIM Bearer Token.

  • Confirm you have administrator access to your Okta organisation.

Skillcast Supports

SAML SSO

  • SP-initiated SSO

  • Just-In-Time (JIT) provisioning (optional)

SCIM 2.0 (Optional)

  • Create, Update, deactivate users

  • Group Push is not supported.


Configure the Skillcast Application in Okta

Add the application

To connect Skillcast to Okta, start by adding the Skillcast SAML integration from the Okta Integration Network.

  • In the Okta Admin Console, go to Applications - Applications.

  • Browse the App Catalog and search for Skillcast.

  • Select Add Integration.

  • Set the application label that your users will see.

  • Enter the Client ID from your CSM.

  • Tick the option to display the application icon if you want it visible to users.

  • Select Done to finish the installation.

The Skillcast integration is published in the Okta Integration Network, so all SAML URLs and identifiers populate automatically.

Generate and send your metadata

Skillcast needs your Identity Provider metadata before SSO can be activated.

To retrieve it:

  • Open the Skillcast application in Okta.

  • Go to the Sign On tab.

  • Select View SAML Setup Instructions under SAML 2.0.

  • Download the metadata XML or copy the metadata URL.

Send the metadata file or link to your Skillcast onboarding contact. You will receive a temporary test login URL once Skillcast has activated the connection.

Assign users and groups

You need to assign users before they can sign in.

  • Open the Assignments tab.

  • Select Assign to People or Assign to Groups.

  • Choose the users or groups that need access.

Assignments must be completed before testing.


Configure SCIM Provisioning (Optional)

SCIM provisioning is only available if it is included in your project scope and you have received a SCIM Bearer Token from your CSM.

Enable SCIM integration

  • Open the Provisioning tab in the Skillcast application.

  • Select Configure API Integration.

  • Tick Enable API Integration.

  • Enter the SCIM Bearer Token from your CSM.

  • Test the API credentials to verify the connection.

  • Save your settings.

Enable provisioning features

Under Provisioning to App, choose the lifecycle actions Okta should perform:

  • Create Users

  • Update User Attributes

  • Deactivate Users

Save your changes.


Final Steps and Testing

After Skillcast receives your IdP metadata:

  • Skillcast activates the SSO connection.

  • You receive a temporary URL for login testing.

  • Once testing is successful, Skillcast moves SSO to live.

  • If SCIM is enabled, provisioning flows (create, update, deactivate) are tested during UAT.

Note:
First name, last name, email address, and external ID map by default. Additional custom attribute mappings may be required depending on your Skillcast setup; these will be provided by your CSM during onboarding.


Tips and Troubleshooting

  • User receives “Not Assigned” errors

    Ensure the user or group has been assigned to the Skillcast application in Okta.

  • Skillcast error page during login

    Verify the user exists in Skillcast; users must have an active Skillcast account before logging in via SSO.

  • SCIM provisioning is not working

    Check connectivity, confirm users are assigned to the application, and ensure provisioning actions such as create, update, and deactivate are enabled.

  • Certain user attributes do not update

    Review attribute mappings in Okta Profile Editor and ensure the correct Skillcast SCIM URN attributes are used.

Limitations

  • SCIM Group Push is not supported in Skillcast.

  • SSO cannot go live until the Skillcast team has activated the connection on their side.


Conclusion

You have now configured the Skillcast integration in Okta, including SAML SSO and optional SCIM provisioning. If you need support during setup or testing, contact your Customer Success Manager by selecting Send us a message via the help icon on your portal, or by emailing [email protected].

Did this answer your question?