Posts Tagged ‘ SAS Addin for Microsoft Office ’

Allowing user to publish content that everyone can automatically see in the portal

Mar
15

Doing some research on the new SAS Addin for Microsoft Outlook 4.3, to trouble shout an issue at a customer site (more on that later) when I came across this post on the SAS Support site.

Sample 36921: Using the SAS® Add-In for Microsoft Office to publish documents that can be accessed from the SAS® Information Delivery Portal

It describes a way to change the default content storage options so that when a user saves a document vis the SAS Addin for Microsoft Office, the conent is automatically available via the SAS portal.

I am a great fan of creating content once and making it easily available to as many users as is useful, via their preferred channel. This is a great technique to help with that approach.

 

 

 

 

Share
Posted by  
0 Comments

I wish the SAS Addin for Microsoft had amnesia

May
09

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?

Share
Posted by  
5 Comments