BookmarkSubscribeRSS Feed
helannivas88
Obsidian | Level 7

Hi,

 

We are connecting to MSSQL server using Windows Authentication mode and we are succeeded in connecting to that.  But we do have a problem whenever we issue the libname statement in SAS EG stating Kerberos ticket expiration

 

Have identified that whenever we login to SSH first and then issue the libname, we don't see any issue in the connection. But when we connect to SAS EG first and then if we issue the libname statement , we do face issue.

 

Kerberos ticket is getting generated/renewed whenever we login to SSH under tmp directory but not getting generated using SAS EG(at first).

 

Is there any SAS configuration file to update Kerberos ticket renewal to rectify this issue??

 

Thanks and Regards,

Helan Nivas G

3 REPLIES 3
alexal
SAS Employee

@helannivas88,

 

You have to configure PAM authentication as described in this SAS note:

 

http://support.sas.com/kb/49/432.html

 

After that, please make sure that "PAM_SETCREDENTIALS=TRUE" is uncommented in your /<SASHome>/SASFoundation/9.4/utilities/bin/sasauth.conf. Also, do not forget to restart the object spawner.

 

Besides of all of, you have to set KRB5CCNAME, you can do that through this script in WorkspaceServer_usermods.sh:

 

workspace_user=$(whoami)
workspace_user_ccaches=$(find /tmp -maxdepth 1 -user ${workspace_user} -type f -name "krb5cc_*" -printf '%T@ %p\n' | sort -k 1nr | sed 's/^[^ ]* //' | head -n 1)

if test ! -z "$workspace_user_ccaches"; then
            echo "Most recent krb5 ccache found for '${workspace_user}' at '${workspace_user_ccaches}'."
            echo "Cache last modified: $(stat -c%y ${workspace_user_ccaches})"
            export KRB5CCNAME=$workspace_user_ccaches
            echo "KRB5CCNAME has been set to ${KRB5CCNAME}."
else
            echo "No krb5 credentials caches were found in /tmp for '${workspace_user}'."
fi
helannivas88
Obsidian | Level 7

Hi,

 

As I said earlier and after updating the script in workspaceserver_usermods.sh, it works perfectly in master (Grid controller) and not in Grid node.

 

But our environment are shared across both the servers (i.e.) the configuration is shared between master and Node.

 

But not sure why the ticket are not behaving same like Grid Controller.Can you please let me know the reason on this. Thanks

 

Regards,

Helan Nivas G

suga badge.PNGThe SAS Users Group for Administrators (SUGA) is open to all SAS administrators and architects who install, update, manage or maintain a SAS deployment. 

Join SUGA 

Get Started with SAS Information Catalog in SAS Viya

SAS technical trainer Erin Winters shows you how to explore assets, create new data discovery agents, schedule data discovery agents, and much more.

Find more tutorials on the SAS Users YouTube channel.

Discussion stats
  • 3 replies
  • 2563 views
  • 1 like
  • 3 in conversation