Configure SCIM User Provisioning with HRIS/IdP for Appspace Cloud

Appspace is now compliant with the SCIM (System for Cross-domain Identity Management) specification, a standard for automating the exchange of user identity information between applications.

As Appspace is now a SCIM compliant application, Appspace can integrate with any SCIM client to automate the provisioning, updating, and de-provisioning of users, as follows:

1. User provisioning – when users are created in the organization’s system of record, SCIM can automatically provision those users to the Appspace platform.
2. User de-provisioning– when users change roles or leave the organization, SCIM allows for the automated suspension of those users from the Appspace platform as soon as the system of record has been updated.
3. User data updates– additional properties that may be used within Appspace can be updated automatically via SCIM once the system of record (HRIS/IdP) has been updated.

SCIM Clients

Appspace customers will now be able to use their HRIS (Human Resources Information System) or IdP (Identity Provider) systems as a source of record to create/import their own user attributes, leveraging Appspace’s integration capabilities that allow user-defined attributes to be created and mapped to external data sources. However, in order to take advantage of these capabilities, Appspace customers need to have an IdP or HRIS system that supports the SCIM protocol. If both IdP and HRIS systems are in place, the IdP acts as the SCIM client to transfer data between the HRIS system and Appspace.

Appspace has tested and officially supports the two leading SCIM compliant IdPs; Microsoft Azure AD and Okta. However, most SCIM compliant IdPs should be able to integrate with Appspace. Most of the leading HCM systems support SCIM integration. Please check with your provider to ensure support and assist with any configuration issues.

SCIM and SAML Single Sign-On (SSO)

Appspace recommends using SCIM with SAML-based Single Sign-On (SSO), which provides access to Appspace through your identity provider (IdP).  While these two protocols work together, it is important to understand the role of each:

• SCIM – user provisioning services
• SSO – user authentication services

Summary

Customers who are implementing the Appspace Employee App, Space Reservations, and the Visitor Management systems, may now leverage their existing IdP or HRIS systems to be their source of record, to create/import their own user attributes to provide flexibility targeting content, creating groups, and applying security measures, in multi-domain scenarios via a standardized service.

This article provides the instructions to enable and configure SCIM capabilities within Appspace.

Configure Identity Provider

Prerequisites

• Identify and configure the user attribute that will be used to map with the IdP or HRIS system on the Appspace console. Configure SAML Attributes for Appspace Cloud.
• Appspace has tested and officially supports the following two leading SCIM compliant IdPs:
  • Microsoft Azure AD
  • Okta
    Note

    Most SCIM compliant IdPs should be able to integrate with Appspace. Most of the leading HRIS systems support SCIM integration. Please check with your provider to ensure support and assist with any configuration issues.

Configure IdP

Please find the following guides when configuring your preferred IdP:

• Microsoft Azure AD – Managing user account provisioning for enterprise apps in the Azure portal document.
  Warning

  Custom SAML attributes that are removed from Azure AD, are not automatically removed from the Appspace console, thus the User profile will still display the attribute and value, however, it would not be updated.
• Okta – Build a SCIM provisioning integration overview document.
  Warning

  Do not change the username in Okta even when Okta allows you to change the usernames. In the event a username is changed, the user may not be able to access the Appspace platform. The administrator must either revert back to the original username or must re-provision the user.

Enable and Configure Single Sign-On (SSO) Authentication

Prerequisites

• Account Owner role with an Appspace Platform user license.
• An Identity Provider (IdP) that is SAML 2.0 compliant.
• IdP metadata, or the SSO URL and the x.509 certificate.
  Important

  Please ensure the NameID in the SAML assertion is the email address of the user.

  Appspace uses the following NameID format: urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress
• Configure a SAML identification attribute flag to identify an IdP user as one that should be created in Appspace. This attribute can be selected by the IdP administrator and should be configured in both the IdP and in Appspace.
• Configure the IdP to pass the correct attributes to Appspace such as attribute mappings for the First Name, Last Name, and Username fields.

Enable SSO

Follow the instructions below to enable and configure SSO (Single Sign On) authentication for Appspace.

1. Log in to the Appspace console.
2. Click the ☰ Appspace menu, and select Users. Click Settings at the bottom of the left menu.
   
3. Click the Account Authentication side panel tab.
4. In the AUTHENTICATION METHOD section, select Single Sign-On (SSO) authentication method from the drop-down menu to enable and configure SSO.
   
5. In the SINGLE SIGN-ON (SSO) SETTINGS section, select the desired Login Method:
   • SSO only – Users will be required to sign in with their single sign-on credentials. Only admins can sign in with an Appspace password.
   • SSO or Appspace Credentials – Admin and users will be able to sign in with either their Appspace or single sign-on credentials.
6. In the IDENTITY PROVIDER (IDP) INFORMATION section, configure the IdP settings using one of the following methods:
   
   
   
   Important

   Please ensure the NameID in the SAML assertion is the email address of the user.

   Appspace uses the following NameID format: urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress
   • Drop or upload the IdP metadata XML file.
   • Manually enter the SSO URL and X.509 Certificate details in the relevant fields.
7. In the GENERATING SERVICE PROVIDER (SP) METADATA section, select the desired Data binding (IdP to SP) option:
   • Redirect – Users are redirected to the Identity Provider. SSO details will be passed in a query string with “?SAMLRequest=……” as part of the URL.
   • Post – SSO details are passed using the POST method. Ensure the Identity Provider has direct access to the Appspace Server for this method to work.
8. Click Save once all SSO configurations have been made.

Configure SCIM User Provisioning