Updating an expired SAS Internal Account with the SAS^® Personal Login Manager might fail when the SAS^® Metadata Server is configured with Direct LDAP Authentication and the –PRIMPD option is set.

Note: SAS supports the use of a limited number of internal accounts for metadata administration using SAS^® Management Console.

This problem occurs when the SAS Metadata Server is configured to use Direct Authentication with either LDAP or Active Directory. In this scenario, you connect with SAS Personal Login Manager using the expired password, and then are prompted for the new password. After you enter the new password, the following error message occurs:

The metadata server log is configured with default logging that lists a WARN event with the rejected connection.

The problem occurs under the following circumstances:

• The SAS Metadata Server is configured with Direct Authentication with either LDAP or Active Directory using the –AUTHPD SAS option as shown in the following example:
–authpd LDAP:mycompany.com
• The connecting user's internal account (for example, myuserID@saspw) has expired.
• The –PRIMPD SAS option is set as shown in the following example:
–primpd mycompany.com
• The SAS Metadata Server is configured to expire SAS Internal Accounts. You can check this by opening the SAS Metadata Server omaconfig.xml file to see whether the following InternalAuthenticationPolicy is set:
• useStdPasswordExpirationDays="T"
• ExpirationDays="60"

Enabling the Audit.Authentication metadata server logger to TRACE level logging shows that the exception with Internal Authentication is due to the expired password that must be changed. The log also indicates that an empty password for the LDAP provider failed.

There are two workarounds:

• One workaround is to remove the –PRIMPD option. Removing the –PRIMPD option requires LDAP users to enter the LDAP domain when authenticating.
• Another workaround is to set ExpirationDays="0", indicating that passwords do not expire.

Click the Hot Fix tab in this note to access the hot fix for this issue.

Operating System and Release Information

A fix for this issue for SAS Threaded Kernel Secure 9.3_M2 is available at: