Features/Single signon

From TempusServa wiki
Revision as of 12:59, 8 November 2024 by Kpe (talk | contribs) (Created page with "== Usage == TS NoCode contains its own user management. In order to minimize the effort in maintaining the profiles, and require less effort for users allready authenticated in other systems. == Oauth2 == There are multiple Oauth 2 sources available • Azure • Office 365 • Google • LinkedIn • Facebook Note than only the Office 365 source can be used to synchronize group membership. === Implementation === Setup will require 2 steps # Setting up the SSO source...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Usage

TS NoCode contains its own user management. In order to minimize the effort in maintaining the profiles, and require less effort for users allready authenticated in other systems.

Oauth2

There are multiple Oauth 2 sources available • Azure • Office 365 • Google • LinkedIn • Facebook

Note than only the Office 365 source can be used to synchronize group membership.

Implementation

Setup will require 2 steps

  1. Setting up the SSO source
  2. Configuring your TS platform

LDAP integration

LDAP integration is not SSO per se, but rather using LDAP as an authentication source.

Implementation

TS as a provider

In case you want other systems to use TS to authenticate users, the platform can be set up to respond to Oauth2 requests.

Implementation