Configure SSO slug during Krisp deployment

Who can use this feature?

Users: Enterprise (only admins)
From version: Win 1.47.4
Other: SSO-enabled team

This article explains how to configure SSO slug for your Krisp team during the installation or update process.

Check this article to learn more about how you can get started with Krisp SSO.

Why to configure SSO slug during Krisp deployment?

By configuring SSO slug during Krisp installation, users can sign in to Krisp app through SSO instead of navigating to the browser and signing in to Krisp app through web browser.
With this flow, users can sign in seamlessly, without having to manually copy/paste the team slug. This can improve the overall user experience with easier and faster access to Krisp app.

  Info

After configuring SSO slug during Krisp deployment, your team users will experience the new sign-in flow changes upon their next sign-in.


How to configure SSO slug during Krisp deployment?

As an admin of SSO enabled team, you can configure Krisp SSO slug while deploying or updating Krisp for your team users by following these steps:

  1. Copy your SSO slug from your Team Settings.
  2. Give your SSO slug as a command line argument while installing/updating/repairing Krisp app.
    See an example command below:

    msiexec /i <PKG_PATH> SSO_SLUG="..."
    Where PKG PATH is a valid path to an MSI package, and SSO_SLUG is equal to your team’s SSO slug in quotation marks.

  Info
If the SSO slug is misconfigured during Krisp deployment, team users will not receive any error messages and will sign in to Krisp app through web browser flow.

Have more questions? Submit a request

Was this article helpful?
1 out of 1 found this helpful