4ALLPORTAL supports various methods for user login and system authentication. In addition to direct login with a username and password, external directory and identity providers can be integrated.
The method used depends on whether users are managed directly in 4ALLPORTAL or whether a central user management system is to be used, and whether automated system access is required.
Supported authentication methods
Username and Password
Users can log in with a username and password managed directly within 4ALLPORTAL.
Admins can manually create users. New users will receive an invitation via email and can then set their password.
Alternatively, users can register themselves if user registration has been set up.
LDAP
LDAP allows the 4ALLPORTAL to be connected to a central user directory, such as Microsoft Active Directory.
LDAP can also be used to synchronize users from the user directory with the 4ALLPORTAL.
Synchronization is provided via the 4App LDAP Sync User.
SAML 2.0
SAML 2.0 enables login via an external identity provider and can be used for centralized user management and single sign-on.
Supported providers include:
Microsoft Active Directory Federation Services (AD FS)
Microsoft Azure Active Directory
Okta
CyberArk
Keycloak
Mapping and multiple authentication services
The authentication services support user synchronization as well as the mapping of users, roles, and languages.
If necessary, it is also possible to configure two or more authentication services in parallel.
OAuth 2.0
With OAuth 2.0, users can log in to the 4ALLPORTAL via an external OAuth 2.0 provider.
Supported providers include:
Facebook
Google
GitHub
Keycloak
OAuth 2.0 is provided via the 4App OAuth 2.0 Authentication Service Provider.
OpenID Connect (OIDC)
While OIDC providers may work, full OIDC support is not currently available.
Please note:
OIDC providers can be integrated if they provide an OAuth 2.0-compatible /userinfo endpoint. Login is handled via OAuth 2.0.
The OIDC ID token is not processed by 4ALLPORTAL. Therefore, user information must be provided via the /userinfo endpoint.
API Key
API keys are not used for logging in to the interface as a user. Instead, they are used for authentication with the 4ALLPORTAL REST API and for automated access between systems.
Each API key is assigned to a specific user. Admins can create, restrict, and revoke API keys.
Admins can create API keys in the following admin snap-in:
Administration > Developer > API
Single Sign-On (SSO)
4ALLPORTAL supports single sign-on via external identity providers based on SAML 2.0 or OAuth 2.0.
SSO enables users to log in using their existing corporate accounts. This enables centralized user management and eliminates the need for a separate 4ALLPORTAL login.
The specific configuration depends on the selected identity provider and may include additional security features, such as multi-factor authentication.
Two-Factor Authentication (2FA)
4ALLPORTAL does not currently offer native two-factor authentication.
However, 2FA can be used via a connected identity provider if login is performed via SAML 2.0 or OAuth 2.0 and the respective provider has configured this feature accordingly.
➡️ Next Steps
Admins can find more information on setup and technical configuration in the technical documentation: