User authentication mechanisms

There are several supported ways to identify user identity in Omniscope:

List of users (local authentication)

This method is about creating a list of usernames and passwords, stored in a simple and safe way in Omniscope.

When users sign-in Omniscope verifies the inputted credentials. Omniscope user names are associated with group permissions, so after authentication is verified, Omniscope will manage the authorisation of the resource.

When "list of users" mechanism is used, the user’s encrypted password is stored on the Omniscope installation. 
Passwords are never stored in clear text, Omniscope uses BCrypt password-hashing function.

OpenID Connect

Session based authentication layer on top of OAuth 2.0, it's the most recent, modern and recommended method to verify user identity. 
There are many Identity Providers you can configure and use to verify your users identify, e.g. Google, Facebook, Microsoft, Okta, Auth0, KeyCloak. 
For more information see the dedicated articles section here.

LDAP Query

Allows you to authenticate against your company's LDAP server.

Here's the documentation written for Omniscope Classic Server which is compatible with Evo too.

Spnego (Single sign on)

Use this to authenticate against your company's Spnego settings.

Here's the documentation written for Omniscope Classic Server which is compatible with Evo too.