How the Security Server User Management Works?

How the Security Server user management works?

Security Server user management is based on roles. One user can have multiple roles and multiple users can be in the same role. Each role has a corresponding system group, created upon the installation of the system. Rights of each user group are described in a configuration file (proxy-ui/config/privileges.yml).

Security Server uses Pluggable Authentication Modules for Linux (Linux-PAM) for user authentication. Linux-PAM supports different authentication mechanisms. By default, pam_unix is used.

Linux-PAM is a suite of shared libraries that enable the local system administrator to choose how applications authenticate users. In other words, without (rewriting and) recompiling a PAM-aware application, it is possible to switch between the authentication mechanism(s) it uses.

• https://github.com/linux-pam/linux-pam/
• https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/System-Level_Authentication_Guide/Pluggable_Authentication_Modules.html

Step-by-step guide

Related articles

• Page:
  How Is the Time-Stamping Service Used in X-Road?
• Page:
  How Is the OCSP Responder Service Used in X-Road?
• Page:
  What Is the Difference Between the Add Member and Add Client Options Available on the Security Server?
• Page:
  How to Set Up a Security Server?
• Page:
  How to Access the Message Body in the Message Log Database and Archive Files?