Authentication overview

Before they are able to log into Vertec, a person's details imust be entered as a user .

Afterwards, the login either occurs directly in Vertec using a user name and password, or is managed via an external service such as LDAP or OpenID.

Using Vertec login

The details for logging in via user name and password are managed on the detail view of the user in accordance with the requirements configured in the System settings . Comprehensive information about this is available in the article Authentication via Vertec login .

2-factor authentication (2FA)

Vertec supports 2FA for logging into cloud clients (Vertec Cloud App, Vertec Web App, Vertec Phone App) via any authenticator app, e.g. Google Authenticator. In particular, if the Vertec instance is accessible via the internet, we strongly recommend requiring a complex password in combination with 2FA. This applies to all Cloud Suite customers and all On-Premises customers, whose Vertec is accessible via the internet in any form.

You can read more about this in the article 2-factor authentication .

Authentication via LDAP server

Vertec users can be linked to users in an LDAP server (e.g. Active Directory). A prerequisite for this is a correctly configured LDAP server. The customer is responsible for this. When logging into Vertec, the user can then log in with their user name and password from LDAP.

Vertec’s 2FA (see above) can also be combined with LDAP. We strongly recommend activating 2FA when authenticating via LDAP.

For more detailed information about this, consult the article Authentication via LDAP server .

Authentication via OpenID Connect

OpenID Connect is an application of the OAuth standard, which focuses on confirming a user’s identity (authentication). Implementation is based on Microsoft 365 and Entra ID (formerly Azure AD). Vertec obtains a token from Entra ID. Several steps are taken to ensure that Vertec and Entra ID can trust each other and that the user has authenticated themself with Entra ID.

The ID token contains a unique user ID, which is assigned to a specific Vertec user and is used to log the user into Vertec. There is no need to log in separately to Vertec if the user is already logged into the other system (Microsoft 365).

You can read more about this in the article OpenID Connect .

Authentication via API tokens for Web API access

API tokens are required to access Vertec via Web API, i.e. in the Vertec XML extension and the BI API extension .  

For more detailed information about this, consult the article API token .

Authentication check for connecting to Vertec in third-party systems

If a third-party system is to enable login to Vertec via the user name and password as well as 2FA, the authentication can be checked via the Cloud Server endpoint /authcheck.

For a detailed description, see Authentication check via Cloud Server .