We expected similar problems cause by users not using their full login name, they skipped to add "@domain", so active directory found someone with the same name, but in a different domain, resulting in the message wrong password. Not that funny was, that the other user had his account locked, due to using a wrong password to many times. We fixed the problem in the config of the sas metadata server by adding:
-SET AD_HOST your_full_domain -AUTHPD ADIR:short_domain_name -PRIMPD short_domain_name
So the question is what has changed since last month to cause the problem? Working with Tech Support on this is probably a better option.
Where does the user / password failure happen? When connecting to the SAS metadata server or later?
Your first statement creates an impression that the user is unable to run code using SAS EG on production server. From the second statement it appears that the user is not able to access the database.
What exactly is the issue?
Can you please post the log.
The SAS Users Group for Administrators (SUGA) is open to all SAS administrators and architects who install, update, manage or maintain a SAS deployment.
Learn how to install the SAS Viya CLI and a few commands you may find useful in this video by SAS’ Darrell Barton.
Find more tutorials on the SAS Users YouTube channel.