This section lists some of the common installation problems that you may experience along with suggested solutions.
This section lists some of the common installation problems that you may experience along with suggested solutions.
If you are unable to determine the solution to a problem, contact Technical Support for help.
Before you contact Support, please collect the following information:
Take a system information snapshot. To do this, run the following command as root:
/opt/quest/libexec/vas/scripts/vas_snapshot.sh
This produces an output file in /tmp.
Make note of the UNIX attributes for the user that cannot log in (if applicable). To do this, capture the output from the following commands:
vastool -u host/ attrs <username> id <username>
Note: Depending on your platform, you may need to run id -a instead of id.
Copy the text from any error messages that you see.
Save the results of running a "double su." To do this, log in as root and run su <username> note any error messages. Then run su <username> again and note any error messages.
Once you have collected the information listed above, contact Support at https://support.oneidentity.com/authentication-services/.
Since Safeguard Authentication Services relies on Active Directory, follow Microsoft’s best practices for keeping the database highly available. The administration tools are not critical to the operation of Safeguard Authentication Services and can quickly be reinstalled from scratch if needed.
You may experience long delays (over a minute) when starting the Safeguard Authentication Services Windows installer or certain Windows management tools such as Control Center. All Safeguard Authentication Services Windows binaries are Authenticode-signed so that you can be sure that the binaries are authentic and have not been tampered with.
This problem occurs when the .NET runtime attempts to verify the Authenticode signature by checking against certificate revocation lists (CRLs) at crl.microsoft.com. If this site cannot be reached, the .NET framework check will time out (up to 60 seconds). This timeout occurs every time a signed assembly is loaded which can lead to very long load times. You can fix this problem by allowing access to crl.microsoft.com.
If the computer is not connected to the internet, you can disable CRL checks for the entire system in Internet Explorer. Go to Options, select the Advanced tab, and under Settings clear the Check for publisher's certification revocation option.
It is also possible to specify a generatePublisherEvidence element in an <app>.exe.config that will disable CRL checks for the specific application that you are running. Keep in mind that if you are using Safeguard Authentication Services components in PowerShell or MMC, you will need to add this configuration for the powershell.exe.config and/or mmc.exe.config. Refer to <generatePublisherEvidence> Element for details.
© ALL RIGHTS RESERVED. 使用条款 隐私 Cookie Preference Center