Did you change your LinkedIn password yesterday? (If you didn’t, you should!) But did it happen to be the same as your corporate password? First, tisk tisk. Second, change your corporate password NOW!
Ok, now that this is done ~ don’t let your saved connection profile for SAS applications lock your corporate account out later today. (The SAS connection profile is used in thick client applications including SAS Information Map Studio, SAS OLAP Cube Studio and SAS Management Console.) Before clicking the OK button to start a SAS connection, select Edit... and enter your new corporate password.
Now SAS Administrators are probably going to be interested in ensuring that passwords are never saved in this system (especially after the LinkedIn fiasco). If this functionality was not disabled during the initial SAS configuration, administrators can go back and make that modification. Modify the XML property SASSEC_LOCAL_PW_SAVE from "T" to "1" to SASSEC_LOCAL_PW_SAVE "F" or "0" within the omaconfig.xml file located in the SAS Metadata Server configuration (Lev1/SASMeta/MetadataServer) and then restart the SAS services. Now the button 'Save user ID and password in this profile' (as seen in the 2nd screenshot above) will not be available for your SAS users and they will be forced to enter their password each time they initiate a connection.