Authentication

Authentication is the process where users prove their identity to log in. This usually involves entering a username and password on the login screen.

Depending on the password policy selected for the user in the User administration form, access to the application will be granted through one of the following types of authentication:

  • Server default: A standard login screen is displayed where the user must enter their username and password.

  • Password + SMS: After the username and password are entered and validated, an additional screen is displayed requesting a verification code. This code is sent in a text message to the mobile phone number registered for the user in the User administration form. If no mobile number is registered, the verification code screen will advise the user to contact the application administrator. However, if the mobile number is invalid, the user will not receive the SMS code. The SMS code remains active for 5 minutes and is valid for one-time use.

  • Password + Auth: After the username and password are entered and validated, an additional screen is displayed requesting a verification code from an authenticator app.

    If the user doesn’t already have an authenticator app, he/she needs to install one on his/her mobile device (IS Tools supports common authenticator apps, such as Microsoft Authenticator, Google Authenticator, Apple Keychain, or Authy), scan the QR code, or manually copy the code we provide into his/her app to verify the pairing. After this pairing, the login authentication code can be generated.

    For future logins, the login authentication code can be generated directly. If user’s device is lost or broken, the pairing can be reset by using Remove Authenticator app registration in User administration after which the user could pair a new device/app as above.

  • SAML: Single Sign-On, where users log in via their company’s Active Directory to enhance security and simplify user administration. Instructions for configuration are provided here.

  • A customized authentication type, e.g., the user’s company requested to IS Tools support to have a password policy with extended expiry date.

If the administrator grants to the user a new role with rights on data tables not previously granted while the user is online, the user must log out and log in again to see such data. Otherwise, it’s enough to reload the form or refresh the menu.