V-Suite offers two ways of authenticating user credentials:

  • Authentication via a Single Sign-On (SSO) provider, such as Azure Active Directory or Active Directory Federation Services (ADFS)
  • Authentication using V-Suite user name and password


Sign-in services are provided through the V-Suite Identity Server.

Authentication via Single Sign-On (SSO) provider

The following diagram illustrates the sign-in and authentication process when you use the Sign in with corporate account button to sign in:


  • User initiates the SSO authentication request using the Sign in with corporate account button.
  • If the user is already authenticated with the Single Sign-On (SSO) provider (possibly due to using another application with the same SSO provider), the system will recognize this and the user will be seamlessly directed to the application without the need for additional login prompts.
  • If the user is not already authenticated, they will securely provide their username and password to the SSO provider via HTTP over SSL (HTTPS).
  • The SSO provider then validates the username and authenticates the user against the external user directory configured (like Azure AD or ADFS).
  • Once the user is authenticated, the system checks whether the authenticated user is registered in V-Suite Web.
  • If the user is registered in V-Suite Web, they are granted access to V-Suite applications and an identity token is issued.
  • If the user is not registered in V-Suite Web but is part of a V-Suite linked security group, they will be redirected to the self-registration page. The user can then provide the necessary details to create a V-Suite Web account. After registration, they will be logged into the system and gain access to the assigned applications.
  • If the user isn't linked to any V-Suite security group and isn't registered in V-Suite Web, an error message is displayed. The message will instruct the user to either contact the V-Suite Web administrator to request access or to sign in through SSO as a different user who has access.
  • If the user opted for the Remember Me feature during sign-in, the identity token is stored in a browser cookie. The next time the user starts the browser, this cookie information is automatically supplied to the identity server. If the token is still valid, access is granted without the need for the user to authenticate with the SSO provider again. Please note, neither the username nor the password are stored in the cookie.


Usage conditions:

  • The system must have a configured Single Sign-On (SSO) Authentication Provider.
  • SSO Authentication is accessible in both Local Area Network (LAN) and Internet access scenarios.
  • The 'Remember Me' option can be disabled by the system administrator.

Authentication using V-Suite user name and password

The following diagram illustrates the sign-in and authentication process when you sign in by using the V-Suite user name and password:

  • User securely provides V-Suite user email and password to the Identity Server via HTTP over SSL (HTTPS).  
  • Identity Server verifies if the specified email belongs to a valid V-Suite user and then authenticates the user against its internal directory of user accounts.  
  • If authenticated, the user will be granted access to V-Suite applications and will obtain an identity token.  
  • If the user selected the Remember Me option when signing in, the identity token is stored in a browser cookie. The next time the user starts the browser, the cookie information is provided to the identity server and if the token is valid, the user will be granted access without having to provide username and password. Identity server will not store the user email or password in the cookie.


Usage conditions:

  • Authentication using V-Suite user name and password is available in both Local Area Network (LAN) and Internet access scenarios.
  • The 'Remember Me' option can be disabled by the system administrator.