Contents x
    Single Sign-On
    • 22 Aug 2024
    • 1 Minute to read
    • Contributors
    • Print
    • Dark
      Light
    Contents
      This documentation version is deprecated, please click here for the latest version.

    Single Sign-On

    • Updated on 22 Aug 2024
    • 1 Minute to read
    • Contributors
    • Print
    • Dark
      Light
    Article summary

    Single sign-on (SSO) is available at no extra cost for customers that leverage LimaCharlie's custom branded offering. If this applies to your organization, and if you are interested in using the SSO, please submit a Custom Branding / SSO Request.

    If your organization does not currently have a custom branded site with LimaCharlie, you can learn about the requirements, costs & get started here.

    Strict SSO Enforcement

    LimaCharlie offers the ability to implement strict SSO enforcement. This means that SSO can be configured as the only authentication option.

    With this capability, you may say that any user with your email domain @example.com must authenticate via Google. This way you can disable the login + password, GitHub, and Microsoft login options for users with your email domain (@example.com) - regardless if they are logging in via your custom branded site, or via app.limacharlie.io

    How it works

    LimaCharlie's single sign-on functionality lets companies add their own SSO option that goes through their authentication server instead of through Google or something else. Identity Platform acts as the coordinator here. After configuring new Providers in Identity Platform, the app only needs to specify a provider ID, and then Identity Platform will handle talking to the company's auth server.

    User experience

    The high-level user experience is as follows:

    • For organizations that choose to use SSO, the SSO will be enforced. Users going to custom branded versions of the LimaCharlie site will be presented with only the option to login through SSO, if their domain has the SSO configuration.

    image.png

    • The same user going to the non-branded site would still be presented with all other authentication options. However, a user would only be able to use the authentification option approved for their domain.

    image.png

    Was this article helpful?
    What's Next