Single Sign-On (SSO)

Single Sign-On (SSO)

By using our Single Sign-On, SSO, integration, end-users are allowed to sign in into your RUN application using the credentials from your own trusted user database. This database is provided by third-party services such as Okta, Microsoft Azure AD, OneLogin, PingIdentity, Google Workspace, and several other identity providers.


TagoIO SSO integrated with 3rd-party services

 

You can also use these services to manage your users' information as well as to allow them to access other services, such as your RUN application.

The configuration on RUN is quite simple, all you have to do is import the Identity Provider (one of the aforementioned third-party services) after configuring an application on the Identity Provider and adding your users. 

Only users registered in the identity provider and that have permission to access the application will be able to sign in to your RUN via the SSO.

The configuration of your SSO will depend on the identity provider used. 

Learn how to configure your SSO to connect with :


    • Related Articles

    • Okta SSO

      When using Okta as the identity provider, follow these steps to configure your SSO:  Access the Admin panel on your Okta account, then browse to the Applications section. Click on Add Application and then Create New App. In the modal, select Web for ...

    • PingIdentity - PingOne SSO

      in progress

    • TagoRun

      The Run module allows you to create and deploy your solution using a customized logo, colors, URL, sign up page, e-mail messages, and more. Run works synchronized with the Access and User management modules. When you configure and deploy your ...

    • User Management

      You can visualize and control all users that sign up in your application under the User Management module. When you create and deploy your solution using TagoRun, all users that sign up will be listed in this area. You can grant or remove access, ...

    • Signup Fields

      Inside of your Sign up page, you can add customized fields for the user on top of the required fields of the form. The Field name will be copied into the User tag key, while the value input by the user during the sign up will be copied to the User ...