User Administration and Authorization in GK/Retail Applications

User Management

Management of the GK/Retail users is carried out by the integrated user management. The data can be replicated from various IdM sources such as LDAP or Active Directory. The data of all components can be updated at the same time but the data must be regularly synchronized. LDAP can be used as the target authentication provider for the Employee Hub login processes. A detailed description can be found in the "User Management - Product Description" documentation.

Password Policies

The password policies of GK/Retail applications can be configured according to the customer requirements. There are the following possibilities for the management of password policies:

  • Maximum number of login attempts
  • Password expiration

User Types

The different user types can be categorized into three groups:

  • Users with access to the Cloud subscription

    At least one Azure account with administrative rights must exist to set up and manage the whole customer landscape on Azure Cloud. This account must have the right to manage resource groups and individual resources such as AKS (manage Kubernetes clusters), virtual networks, IP addresses, etc.

  • Users with access to GK/Retail Employye Hub

    End users using GK/Retail business services with access rights to store-specific or global data.

  • Users with access to the used databases

    After the installation, default accounts exist for access to the required database components. It is recommended to change the predefined passwords of the used DBMS during the installation or immediately afterwards.

  • Users with access to the store host system (for store components only)

    At least one user account with administrative rights for the installation of store system services must exist to install/uninstall the different services. The services require the anonymous system account, which is available in the standard configuration of Microsoft Windows Server.

User Data Synchronization

The relation between users and roles and the initial password are imported to the GK/Retail applications via the standard user import interface. Users can also be managed by maintenance functions available in Employee Hub.

End-User Authentication

GK/Retail components use their own user management which is independent of the host's operating system and of the Azure Cloud. In this user management, defined rights for the GK/Retail functions access and use are granted and configured for the user. The authentication of GK/Retail users is carried out by username/password authentication.

All credentials of all users are stored encrypted in the GK/Retail database.

Employee Hub is a source of end-user authentication. It performs authentication via an OAuth 2.0 JWT token.

Authorizations

The authorization concept of GK/Retail applications is based on the assignment of authorizations to users carried out according to roles. The individual roles can be maintained in the administrator menu of the Storemanager Client application. The Store Enterprise Server application provides this information to all connected devices.

Single Sign-On

GK OAuth 2.0 JWT technology is used on Employee Hub for safe transfer of authentication between different application types and/or instances. The OAuth 2.0 JWT token is provided after successful authentication by the Authentication Service.

The OmniPOS Client uses an OAuth 2.0 JWT token for authorization to remote services.