morinia
asked on
Windows credential loss after accessing a Table in SAS
Experts,
I am having a serious issue in SAS since my password was reset. My windows credentials are used to give access rights to a table which I am accessing through SAS Enterprise Guide. Until my windows password was reset, I had no issues. Once the database is accessed multiple times in SAS (the step does run to completion), Windows now requires authentication and I am thusly locked out of my windows account.
ANY IDEAS ANYBODY???
I am having a serious issue in SAS since my password was reset. My windows credentials are used to give access rights to a table which I am accessing through SAS Enterprise Guide. Until my windows password was reset, I had no issues. Once the database is accessed multiple times in SAS (the step does run to completion), Windows now requires authentication and I am thusly locked out of my windows account.
ANY IDEAS ANYBODY???
ASKER
Jackie,
The connection profile has been updated. The problem occurs only when a specific table is read. It appears it is picking up incorrect credentials from somewhere and then pick up the correct credentials.
I will try to see if I can get the DBA take away the permissions to that database and then give them back.
The connection profile has been updated. The problem occurs only when a specific table is read. It appears it is picking up incorrect credentials from somewhere and then pick up the correct credentials.
I will try to see if I can get the DBA take away the permissions to that database and then give them back.
You need to runS SAS authorization facility to check the authorization for that particular table.
http://support.sas.com/documentation/cdl/en/bidsag/61236/HTML/default/viewer.htm#a003108616.htm
http://support.sas.com/documentation/cdl/en/bidsag/61236/HTML/default/viewer.htm#a003108616.htm
do you have a metadata server? do you have the LIBNAME statement for the library in question?
quite a few possibilities can happen here - if there's no LIBNAME, or the LIBNAME statement indicates META as the engine, then you'll need to look at the SAS Management Console as it's likely your password has been coded into an authentication domain in the user manager.. if there's a LIBNAME statement with something else as the engine (ODBC for e.g.), then your password could have been coded there..
quite a few possibilities can happen here - if there's no LIBNAME, or the LIBNAME statement indicates META as the engine, then you'll need to look at the SAS Management Console as it's likely your password has been coded into an authentication domain in the user manager.. if there's a LIBNAME statement with something else as the engine (ODBC for e.g.), then your password could have been coded there..
ASKER
IT is still working on problem. I did remember an ODBC driver that is using domain credentials. I am waiting for them to update it since I don't have admin rights to my machine. This sounds like an explanation for unsuccessful logins.
could you provide the LIBNAME statement, if it's in your code, or anywhere else, like some autoexec or other SAS codes? if not, if you connecting via the metadata server, you might need to go to the SAS Management Console to get it
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
This was the problem.
The problem was finally resolved by deleting and recreating the data in APPDATA for SAS. It seems old credentials were stored in there and being passed to Windows each time I accessed any folder, server or database outside of SAS. After five unsuccessful attempts I would lock.
The problem was finally resolved by deleting and recreating the data in APPDATA for SAS. It seems old credentials were stored in there and being passed to Windows each time I accessed any folder, server or database outside of SAS. After five unsuccessful attempts I would lock.
You are locked out because the group policy of your AD will lock out the user if there are a number of incorrect logon attemps from your SAS Enterprise Guide.