User attributes

Scalekit simplifies Single Sign-On (SSO) by managing user information between Identity Providers (IdPs) and B2B applications. The IdPs provide standard user properties, such as email and firstname, to your application, thus helping recognize the user.

Consider that we want to get employee number of the user logging into the application. This guide demonstrates how to add your own custom attribute (such as employee number) and map its value from the Identity Provider.

Broadly, we’ll go through two steps:

1. Create a new attribute in Scalekit
2. Set up the value that the Identity Provider should relay to this attribute

Create a new attribute

Let’s begin by signing into Scalekit dashboard:

1. Navigate to the “SSO” section
2. In the “User Attributes” section, click on “Add Attribute”
3. Add “Employee Number” as Display name

You’ll now notice “Employee Number” in the list of user attributes. Scalekit is now ready to receive this attribute from your customers’ identity providers (IdPs)

Set up IdP attributes

Now, we’ll set up an Identity Provider to send these details. For the purposes of this guide, we’ll use Okta as IdP to send the employee_number to Scalekit. However, similar functionality can be achieved using any other IdP.

Note that in this specific Okta instance, the “Employee Number” is a default attribute that hasn’t been utilized yet. Before we proceed forward, it’s important to modify the profile’s “employee_number” attribute with any desired number for this example (For example, 1729). For a detailed guide on how to achieve this, consult Okta’s dedicated help article on updating profile attributes.

Alternatively, you can add a new custom attribute in the Okta Profile Editor.

Test SSO for new attributes

In the Scalekit dashboard, navigate to Organizations.

1. Select the Organization that you’d like to add custom attribute
2. Navigate to the SSO Connection
3. Go to Test Connection - you’ll find this if the IdP has already been established

Upon testing the connection, if you notice the update user profile (employee_number as 1729 in this example), this signifies a successful test.

Subsequently, these details will be integrated into your B2B application through Scalekit. This ensures seamless recognition and handling of customer user attributes during the SSO authentication process.