Difference between revisions of "Features/Single signon"
Jump to navigation
Jump to search
(→Oauth2) |
|||
| Line 4: | Line 4: | ||
== Oauth2 == | == Oauth2 == | ||
There are multiple Oauth 2 sources available | 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. | Note than only the Office 365 source can be used to synchronize group membership. | ||
Revision as of 19:08, 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
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.
- Use LDAP to authencicate
- Import and link groups
Implementation
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.