Difference between revisions of "Features/Single signon"
Jump to navigation
Jump to search
(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...") |
|||
| Line 22: | Line 22: | ||
=== Implementation === | === Implementation === | ||
== TS as | == 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. | In case you want other systems to use TS to authenticate users, the platform can be set up to respond to Oauth2 requests. | ||
=== Implementation === | === Implementation === | ||
Revision as of 18:55, 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
- Setting up the SSO source
- Configuring your TS platform
LDAP integration
LDAP integration is not SSO per se, but rather using LDAP as an authentication source.
Implementation
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.