サポートと今すぐチャット
サポートとのチャット

Safeguard Authentication Services 5.1 - Administration Guide

Privileged Access Suite for Unix Introducing One Identity Safeguard Authentication Services Unix administration and configuration Identity management Migrating from NIS Managing access control Managing local file permissions Certificate Autoenrollment [[[Missing Linked File System.LinkedTitle]]] Managing Unix hosts with Group Policy
Safeguard Authentication Services Group Policy
Group Policy Concepts Unix policies One Identity policies
Display specifiers Troubleshooting Glossary

Version 3 Compatibility Mode

When upgrading to or installing Safeguard Authentication Services 4.x, you can choose not to configure Active Directory for Safeguard Authentication Services and run your Safeguard Authentication Services client agent in Version 3 Compatibility Mode. While this prevents you from running the Control Center and accessing its many features and tools, you can join a host to an Active Directory domain when operating in Version 3 Compatibility Mode.

Note: When you run the join command without first creating a One Identity Application Configuration, Safeguard Authentication Services displays a warning.

Without the Safeguard Authentication Services application configuration the following information is stored locally:

  • Application Licenses
  • Settings controlling default values and behavior for Unix-enabled users and groups
  • Schema configuration
Best practice

Because Version 3 Compatibility Mode does not allow you run the Control Center and access its many features and tools, One Identity recommends that you create the application configuration so you can utilize full Safeguard Authentication Services functionality.

There are two ways to create the application configuration:

  • When you start the Control Center from a Windows workstation, the Set up Safeguard Authentication Services Active Directory Configuration Wizard starts automatically to lead you through the process of configuring Active Directory for Safeguard Authentication Services.
  • Alternatively, you can run vastool configure ad from the Unix command line to create the One Identity Application Configuration in Active Directory.

Unix agent requirements

Note: To install Safeguard Authentication Services on Unix, Linux, or macOS, you must have root access rights.

NOTE: With Safeguard Authentication Services 4.2 and later, Linux platforms require glibc 2.4 (or later).

The following table provides a list of supported Unix and Linux platforms for Safeguard Authentication Services.

Table 5: Unix agent: Supported platforms

Platform

Version

Architecture

Alma Linux

8, 9

x86_64, AARCH64, PPC64le

Amazon Linux

AMI, 2, AL2022

x86_64

Apple MacOS

10.15, 11.x, 12.x, 13.x

x86_64, ARM64

CentOS Linux

6, 7, 8, 9

Current Linux architectures: s390x, PPC64, PPC64le, x86, x86_64, AARCH64

CentOS Stream

8, 9

x86_64

Debian

Current supported releases

x86_64, x86, AARCH64

Fedora Linux

Current supported releases

x86_64, x86, AARCH64

FreeBSD

12.x, 13.x

x32, x64

HP-UX

11.31

PA, IA-64

IBM AIX

6.1 TL9, 7.1 TL3, TL4, TL5, 7.2, 7.3

Power 4+

OpenSuSE

Current supported releases

x86_64, x86, AARCH64

Oracle Enterprise Linux (OEL)

6, 7, 8, 9

Current Linux architectures: s390x, PPC64, PPC64le, x86, x86_64, AARCH64

Oracle Solaris

10 8/11 (Update 10),

11.x

SPARC, x64

Red Hat Enterprise Linux (RHEL)

6, 7, 8, 9

Current Linux architectures: s390x, PPC64, PPC64le, x86, x86_64, AARCH64

Rocky Linux

8, 9

x86_64, AARCH64

SuSE Linux Enterprise Server (SLES)/Workstation

12, 15

Current Linux architectures: s390x, PPC64, PPC64le, x86, x86_64, AARCH64

Ubuntu

Current supported releases

x86_64, x86, AARCH64

Note: For maximum security and performance, before you begin the installation, make sure that you have the latest patches for your operating system version. One Identity recommends that you run the Preflight utility to check for supported operating systems and correct operating system patches.

For more information, see Running Preflight in the Safeguard Authentication Services Installation Guide.

Unix components

Safeguard Authentication Services includes the following Unix components.

Table 6: Unix components
Unix component Description

vasd

The Safeguard Authentication Services agent background process that manages the persistent cache of Active Directory information used by the other Safeguard Authentication Services components. vasd is installed as a system service. You can start and stop vasd using the standard service start/stop mechanism for your platform. vasd is installed by the vasclnt package.

vastool

The Safeguard Authentication Services command line administration utility that allows you to join a Unix host to an Active Directory Domain; access and modify information about users, groups, and computers in Active Directory; and configure the Safeguard Authentication Services components. vastool is installed at /opt/quest/bin/vastool. vastool is installed by the vasclnt package.

vasgmsaupdate

Service to keep gMSA passwords always up to date

vgptool

A command line utility that allows you to manage the application of Group Policy settings to Safeguard Authentication Services clients. vgptool is installed at /opt/quest/bin/vgptool. vgptool is installed by the vasgp package.

oat (Ownership Alignment Tool)

A command line utility that allows you to modify file ownership on local Unix hosts to match user accounts in Active Directory. oat is installed at /opt/quest/libexec/oat/oat. oat is installed by the vasclnt package.

LDAP proxy

A background process that secures the authentication channel for applications using LDAP bind to authenticate users without introducing the overhead of configuring secure LDAP (LDAPS). The LDAP proxy is installed by the vasproxy package.

NIS proxy

A background process that acts as a NIS server which can provide backwards compatibility with existing NIS infrastructure. The NIS proxy is installed by the vasyp package.

SDK package

The vasdev package, the Safeguard Authentication Services programming API.

Permissions matrix

The following table details the permissions required for full Safeguard Authentication Services functionality.

Table 7: Required permissions
Function Active Directory permissions Local client permissions
Safeguard Authentication Services Application Configuration: creation Location in Active Directory with Create Container Object rights N/A
Safeguard Authentication Services Application Configuration: changes
  • Unix Global Settings
  • Licensing
  • Schema Attributes, including Unix Attributes
 Update permission to the containers created above (no particular permissions if you are the one who created it) N/A
Schema optimization Schema Administrator rights N/A
Display Specifier Registration Enterprise Administrator rights N/A
Editing Users Administrator rights N/A

Create any group policy objects

Group Policy Creator Owners rights

N/A

RFC 2307 NIS Import Map Wizard Location in Active Directory with Create Container Object rights (you create containers for each NIS map) N/A
Unix Account Import Wizard Administrator rights (you are creating new accounts) N/A
Logging Options Write permissions to the file system folder where you want to create the logs N/A
vasd daemon

The client computer object is expected to have read access to user and group attributes, which is the default.

In order for Safeguard Authentication Services to update the host object operating system attributes automatically, set the following rights for "SELF" on the client computer object: Write Operating System, Write operatingSystemHotfix, and Write operatingSystemServicePack.

 vasd must run as root
QAS/VAS PAM module N/A (updated by means of vasd) Any local user
QAS/VAS NSS module

vastool nss

 N/A (updated by means of vasd) Any local user
vastool command-line tool Depends on which vastool command is run Any local user for most commands

vastool join

vastool unjoin

Computer creation or deletion permissions in the desired container root

vastool configure

vastool unconfigure

N/A root

vastool search

vastool attrs

Read permission for the desired objects (regular Active Directory user) Any local user
vastool setattrs Write permissions for the desired object Any local user
vastool cache N/A Run as root if you want all tables including authcache
vastool create Permissions to create new users, groups, and computers as specified Any local user; root needed to create a new local computer
vastool delete Permissions to delete existing users, groups, or computers as specified; permissions to remove the keytab entry for the host object created (root or write permissions in the directory and the file) Any local user
vastool flush The client computer object is expected to have read access to user and group attributes, which should be the default root

vastool group add

vastool group del

Permission to modify group membership Any local user
vastool group hasmember Read permission for the desired objects (regular Active Directory user) Any local user
vastool info { site | domain | domain -n | forest-root | forest-root -dn | server | acl } N/A Any local user
vastool info { id | domains | domains -dn | adsecurity | toconf } Read permission for the desired objects (regular Active Directory user) Any local user

vastool isvas

vastool inspect

vastool license

N/A Any local user

vastool kinit

vastool klist

vastool kdestroy

Local client needs permissions to modify the keytab specified; default is the computer object, which is root. Any local user
vastool ktutil N/A root if you are using the default host.keytab file
vastool list (with -l option) Read permission for the desired objects (regular Active Directory user) Any local user
vastool load Permissions to create users and groups in the desired container Any local user

vastool merge

vastool unmerge

N/A root
vastool passwd Regular Active Directory user Any local user
vastool passwd <AD user> Active Directory user with password reset permission Any local user

vastool schema list

vastool schema detect

Regular Active Directory user Any local user
vastool schema cache Regular Active Directory user root (to modify the local cache file)
vastool service list Regular Active Directory user Any local user
vastool service { create | delete } Active Directory user with permission to create/delete service principals in desired container N/A
vastool smartcard N/A root
vastool status N/A root
vastool timesync N/A root, if you only query the time from AD, you can run as any local user
vastool user { enable | disable } Modify permissions on the AD Object Any local user
vastool user { checkaccess | checkconflict } N/A Any local user
vastool user checklogin Access to Active Directory users password Any local user
vasgmsaupdate service On the Windows Domain Controller, the host machine must be set to be able to access gMSA user Service must be started as root
関連ドキュメント

The document was helpful.

評価を選択

I easily found the information I needed.

評価を選択