6 thoughts on “Self-Service Account/Login Management with the SAS Personal Login Manager”

  1. Paul, I think you alluded to this in your post, but here’s a clarification. You can also manage your logins with SAS Enterprise Guide by:

    – Select Tools->SAS Enterprise Guide Explorer. The SAS Enterprise Guide Explorer windows appears.
    – Select File->Manage Logins. The Login Manager window appears.

    The Login Manager window works very similarly to the Personal Login Manager application.

  2. Hi Chris,

    Thanks for providing more info on how to access the login management facility within SAS Enterprise Guide.


  3. How do you use the account information in SAS Personal Login Manager in a program?

  4. Hi Charles,

    It depends on how you want to use it. Can you be a bit more specific?

    From an admin perspective, reporting on logins (without using any encrypted stored credentials), you can use the standard SAS %MDUEXTR macro to extract the login data (among other things) into a SAS table. Metacoda also provides a %metacodaIdentityLoginExtract macro in the idsync-utils github project that extracts some extra attributes (and also handle long UTF-8 strings).

    From a user perspective to use the (outbound login) credentials to get access to third party systems look for authentication domain support in the SAS feature you are using. For example SAS/ACCESS AUTHDOMAIN= LIBNAME Option.


  5. I can’t seem to find the login manager in SAS EG 8.1 after the upgrade recently.
    I need to set the password for the DefaultAuth.

  6. Hi Gary,

    Can you see the SAS Enterprise Guide Explorer? If not it may be that your group and role memberships do not provide access to the “Access SAS Enterprise Guide Explorer” capability. Talk to your SAS platform admins about whether you are running with a restricted set of capabilities in SAS EG. Our Metacoda Security Plug-ins are great for troubleshooting roles and capabilities so let me know if you’d like an eval to investigate further.

    Alternatively, you can use the SAS Personal Login Manager app to manage logins.

    I might also ask the question why you need to set the password for your DefaultAuth login in metadata? Most sites leave this blank for users and rely on in-memory cached credentials from the initial login to the metadata server. This avoids having to maintain an up to date password in metadata and the problems that come with that. This is not always possible, of course, and yours may be one of those situations, but I ask because I have seen people unnecessarily maintaining DefaultAuth login passwords in metadata when they could have just use cached credentials with well aligned auth domains.


Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.