Safeguard Authentication Services 5.0.2 - Administration Guide

Unable to join the domain

If you are unable to join the domain, run the preflight utility to validate your environment.

For more information, see The Safeguard Authentication Services Pre-Installation Diagnostic Tool in the Safeguard Authentication Services Installation Guide .

Then, verify the following:

• Check that the Active Directory account specified during join has rights to join the computer to the domain.
• Check that the Unix host is able to properly resolve the domain name through DNS.

If you are joining to a specific domain controller you must ensure that Safeguard Authentication Services can locate and read the configuration information in Active Directory. You should do one of the following:

• Make sure the domain controller you specify is a global catalog.
• Create the Safeguard Authentication Services application configuration in the domain to which you are joining.

  For more information, see the About Active Directory Configuration section in the Safeguard Authentication Services Installation Guide.

• Properly configure DNS to return srv-records and avoid joining to a specific domain controller.

Unable to log in

If you are unable to log in as an Active Directory user after installing, check the following:

1. Log in as root on the Unix host.
2. Check the status of the Safeguard Authentication Services subsystems. To do this, run the following command:

   vastool status

   Correct any errors reported by the status command, then try logging in again.

3. Ensure the user exists locally and is allowed to log in. To check this, run the following command:

   vastool user checklogin <username> 

   The output displays whether the user is a known Active Directory user. If not, you may need to map the user to an Active Directory account or Unix-enable the Active Directory account. If the user is known, an access control rule may prevent them from logging in. The output of the command displays which access control rules are in effect for the user.

You may need to restart window managers such as gdm in order for the window manager to reload NSS modules. Until the window manager reloads the NSS configuration, you will be unable to log in with an Active Directory user. Other services such as cron may also be affected by NSS changes. If you are unsure which services need to be reloaded, reboot the system.

Unix Account tab is missing in ADUC

If the Unix Account tab is missing when viewing the properties of a user or group in Active Directory Users and Computers, the most likely cause is that the extension module (AducExtensions.dll) was unable to load. Typically this is due to an invalid or corrupt installation. To resolve this issue, check the following:

• Ensure that Safeguard Authentication Services has been installed on the local computer.
• Ensure that you are logged in as a domain user or that ADUC is running as a domain user.
• The Safeguard Authentication Services installation may have become corrupted. Remove and re-install Safeguard Authentication Services.
• Certain software is required in order for the Unix Account tab to load. If any of the following software has been removed, please re-install it:
  • Windows PowerShell
  • VisualStudio C++ Runtime
  • .NET Framework v4.5
• If you are working with One Identity Active Roles Server MMC Console, ensure that display specifiers have been installed and that you have restarted the Active Roles Service. Until you do this, the Unix Account tab will not appear in Active Roles Server MCC Console.
• If the Unix Account tab still does not appear, open Control Center and enable debug logging from the Preferences. Attempt to load the Unix Account tab, then send the generated log files to VARcompany.support.

vasypd has unsatisfied dependencies

If you receive the following error message while installing the Safeguard Authentication Services vasypd Unix component, the rpcbind service may not be enabled.

svcadm: Instance "svc:/quest/vas/vasypd:default" has unsatisfied dependencies.
Error 4 starting vasypd

To enable the rpcbind service

1. Check the dependencies of vasypd:

   # svcs -d quest/vas/vasypd
   STATE          STIME    FMRI
   disabled       Sep_14   svc:/network/rpc/bind:default
   online         Sep_14   svc:/milestone/single-user:default
   online         Sep_14   svc:/system/filesystem/local:default
   

2. If rpcbind is disabled, run this command to enable it:

   # /usr/sbin/svcadm enable -s /network/rpc/bind

3. Run the following command to start vasypd:

   # /etc/init.d/vasypd start