Difference between revisions of "Features/Single signon"

From TempusServa wiki
Jump to navigation Jump to search
Line 21: Line 21:


=== Implementation ===
=== Implementation ===
[Integration/LDAP|Learn about how to set up LDAP integration]


== TS as Oauth2 provider ==  
== TS as Oauth2 provider ==  

Revision as of 19:06, 8 November 2024

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

[Integration/LDAP|Learn about how to set up LDAP integration]

TS as Oauth2 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