31

Changes in SCIM User Provisioning Behavior

Do you use System for Cross-domain Identity Management (SCIM) in Kissflow for user provisioning? We recently made some behavioral changes to Kissflow’s SCIM-based user provisioning. Kindly take a few moments to read and understand this change. 

Previously, new users added using SCIM were ‘activated’ by default. There were various limitations to this approach to SCIM user provisioning. Specifically, if the number of new users pushed from your SCIM-based identity provider (IdP) to Kissflow exceeds the number of available Kissflow user licenses, only a subset of new users was added to Kissflow. 

As a result, users that were unable to be accommodated due to user license limits were omitted and were not added to Kissflow. Furthermore, Account Admins require control over who can be activated. The previous behavior prevented them from inviting all of their users via SCIM and then selecting and activating a handful of them.

Users who are added to Kissflow via SCIM will now be assigned the 'Invited' status by default, thanks to the new behavior update. Account Admins can then choose whether to activate all or a subset of the users added through the user management table.

We encourage you to check out our help docs to learn more about this change.

If you have any questions or feedback do let us know in the comments below. We'll be happy to answer them.

Content aside

  • 31 Likes
  • 2 yrs agoLast active
  • 3Replies
  • 96Views