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...") |
|||
| (7 intermediate revisions by the same user not shown) | |||
| 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. | ||
| Line 16: | Line 16: | ||
# Setting up the SSO source | # Setting up the SSO source | ||
# Configuring your TS platform | # Configuring your TS platform | ||
In Designer > Modules > Configuration set up the following properties | |||
* oauth____Allow: Set to true | |||
* oauth____Tenant: From step 1 above | |||
* oauth____Secret: From step 1 above | |||
* oauth____Client: From step 1 above | |||
== LDAP integration == | == LDAP integration == | ||
LDAP integration is not SSO per se, but rather using LDAP as an authentication source. | LDAP integration is not SSO per se, but rather using LDAP as an authentication source. | ||
* Use LDAP to authencicate | |||
* Import and link groups | |||
=== Implementation === | === Implementation === | ||
[[Integration/LDAP|Learn about how to set up LDAP integration]] | |||
== 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 === | ||
Contact TS support team to get a link to the required Wordpress SSO plugin | |||
Also | |||
* oauthWPAllow: Set true | |||
* oauthWPClient: Set to anything | |||
* oauthWPSecret: Set to anything | |||
* oauthWPHost: URL of the Wordpress server | |||
Latest revision as of 19:21, 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
In Designer > Modules > Configuration set up the following properties
- oauth____Allow: Set to true
- oauth____Tenant: From step 1 above
- oauth____Secret: From step 1 above
- oauth____Client: From step 1 above
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.
Implementation
Contact TS support team to get a link to the required Wordpress SSO plugin
Also
- oauthWPAllow: Set true
- oauthWPClient: Set to anything
- oauthWPSecret: Set to anything
- oauthWPHost: URL of the Wordpress server