I have talked to a number of customers that are having a problem with the SAS Addin for Microsoft Office (AMO) remembering a users password and then locking them out of their account.
When a user configures their connection to the SAS Server in AMO they can save their password, so they effectively gain a form of single sign on. (The password is stored as an encrypted text string in an XML file).
A number of customers I talked to also have some form of LDAP authentication setup (i.e. Active Directory), Unfortunately when a user changes their password on the LDAP server, AMO doesn’t know about it. It keeps trying to authenticate the user with their old password until the users account gets locked.
SAS Enterprise Guide also enables the user to store their connection credentials, but it seems to prompt the user to re-enter their credentials if the authentication with the server fails, therefore the users account doesn’t get locked.
We are working through some work arounds for this to see if we can fix the AMO issue, but has anybody else struck this?
Anybody else fixed it?
Sorry, I was just turned onto this blog.
Have you considered writing an EG add-in and use it to authenticate instead of the built-in EG functionality? Authenticating to LDAp is pretty straightforward in .NET so you could detect an authenticate failure and kick it back.
I would also just send Stephen McDaniel an email or post it on SAS-L.
Alan
Thanks Alan.
Good point, Ill contact Stephen and see if he knows of a work around for the Office add-in, I hadn’t thought of contacting him.
Most of the lock out issues seem to happen in AMO rather than EG, but thats a great idea for an EG plugin, ill add it to our development list.
Cheers
Shane
Shane, did you ever make any headway on this problem? I’d like to know of a fix as well.
Hi Chris
I have a cunning plan to manage this by deleting the password files each time a user los in, but we haven’t got around to testing it yet.
Ill let you know when we do and whether it works or not.
Cheers
Shane
Has anyone made progress on this issue? I am dead in the water with (2) users..one that had bad password on initial entry into EG and one that used an incorrect user id. Now both accounts connect fine to the metadata server from EG, but stop dead when trying to access any EG projects on the App server.
We use Active Directory for authentication as our and maintain only user id’s in the SMC. Where are the password files located that you mention?