To restart services, enter:
vastool daemon restart vasd
To restart services, enter:
vastool daemon restart vasd
When user identity information is not stored centrally within Active Directory, it is possible for Active Directory users to have Posix identity attributes automatically generated for them when interacting with UNIX hosts, allowing the user to authenticate with an Active Directory password.
This is convenient in situations where you can not utilize enterprise user and group identification from Active Directory. For example, when you do not have sufficient rights to modify User identity objects, or are unable to create the Safeguard Authentication Services Application Configuration object, you can configure Safeguard Authentication Services to auto-generate Posix identity attributes on the UNIX host for Active Directory users.
The following attributes are auto-generated:
UID Number: This attribute is derived from a hash of the Active Directory Users Globally Unique Identifier (GUID).
GID Number: This attribute is derived from the hash of the Active Directory Group GUID that is assigned as the Windows Primary Group object.
Gecos: The gecos field is populated by the users CN, but is configurable by using the [vasd] realname-attr vas.conf setting.
UNIX Home Directory: This attribute is a concatenation of the per-machine configurable home directory base option, [vasd] autogen-posix-homedir-base, and the users sAMAccountName value.
Login Shell: This attribute is set by the per-machine [vasd] autogen-posix-default-shell configuration option.
The generated attributes are stored locally on each UNIX host and remain in effect until manually removed by the system administrator.
Once a host has Posix identity attributes generated for an Active Directory user or group, they remain in effect until you manually remove them. This ensures that you take the proper steps when migrating user identities, specifically when you realign the file and directory ownerships to the new UID and GID values.
To migrate an auto-generated user to use an enterprise identity
Make sure that you have realigned the file and directory ownerships to the new UID and GID values, including the user's home directory. For more information, see For more information, see Managing local file permissions..
Locate the user record in the /etc/opt/quest/vas/autogen.passwd file, and remove it.
Force Safeguard Authentication Services to update the user by means of logging in or by running:
vastool list –f user <username>
This section describes how to migrate auto-generated group identities.
To migrate an auto-generated group to use an enterprise identity
Make sure that you have realigned the file and directory ownerships to the new UID and GID values, including the user's home directory.
For more information, see Managing local file permissions.
Locate the user record in the /etc/opt/quest/vas/autogen.group file, and remove it.
Force Safeguard Authentication Services to update the user by means of logging in or by running:
vastool list –f group <groupname>
© ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center