provides a number of methods to configure user access. The system provides integration with common authentication standards, including
Microsoft LDAP, Google OAuth and
SAML, as well as other
Single Sign-On (SSO) providers. In addition, administrators can configure
hotlinks and
access URLs, and set up
two-factor authentication (2FA).
...
User information - including login, password and other data - has its source in one of two places:
- Users who actively log into into will have a user record in one of the subtables of the People table. Users are generally imported, created manually, or generated through some other automated process.
- User data may also be stored in an external system, such as in LDAP or Microsoft Active Directory, which is used as the master set of user information. An Identity Provider stores the user's login and password across several applications or systems.
Even if a user is authenticated through LDAP or ADS,
creates a user record for them that is then used in rules and other parts of the system as if the user were a native user.
Anchor |
---|
| Custom login blocks |
---|
| Custom login blocks |
---|
|
How do Users Access the System?
...
After this, they can enter and confirm their new password.
Show If |
---|
|
Page intentionally left blank |
Hide If |
---|
|
Related articles Content by Label |
---|
showLabels | false |
---|
max | 5 |
---|
spaces | currentSpace() |
---|
showSpace | false |
---|
sort | modified |
---|
reverse | true |
---|
type | page |
---|
cql | label = "access" and type = "page" and space = currentSpace() |
---|
labels | access |
---|
|
|