<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic LDAP Authentication in Linux environment (for SAS Forecast Server) in Administration and Deployment</title>
    <link>https://communities.sas.com/t5/Administration-and-Deployment/LDAP-Authentication-in-Linux-environment-for-SAS-Forecast-Server/m-p/577723#M16861</link>
    <description>&lt;P&gt;Hi, I am implementing SAS Forecast Server on a Google Cloud Platform (GCP) Compute Instance/VM.&amp;nbsp; I am having problem configuring sasauth.conf to connect back to our on-prem LDAP server for password authentication.&amp;nbsp; One item of note is that the ldap server IP is actually the load balancer for our ldap servers.&amp;nbsp; Not sure if this is significant for my situation or not.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am able to perform an ldapsearch from the command line with an embedded fetch of the target DN as follows:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;ldapsearch -x -LLL \&lt;BR /&gt;&amp;nbsp;&amp;nbsp;-H ldaps://&amp;lt;ldaphost.domain.com&amp;gt;:636 \&lt;BR /&gt;&amp;nbsp;&amp;nbsp;-D "&lt;I&gt;$(ldapsearch -x -LLL \&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;-H ldaps://&amp;lt;ldaphost.domain.com&amp;gt;:636 \&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;-b 'o=,c=us' \&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;-s sub 'uid=&amp;lt;tgt_uid&amp;gt;' dn | grep dn | \&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;cut -d' ' -f2-)&lt;/I&gt;" \&lt;BR /&gt;&amp;nbsp;&amp;nbsp;-s sub "uid=&amp;lt;tgt_uid&amp;gt;" \&lt;BR /&gt;&amp;nbsp;&amp;nbsp;-b "o=,c=us" \&lt;BR /&gt;&amp;nbsp;&amp;nbsp;-w &amp;lt;user_psw&amp;gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Please note also that I have been unable to get an ldapsearch command to work using the form &lt;STRONG&gt;&lt;I&gt;'-h &amp;lt;ldaphost.domain.com&amp;gt; -p 636'&lt;/I&gt;&lt;/STRONG&gt; for the ldap host reference.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The above ldapsearch command fetches the DN first (and strips off the chars 'dn: '), and then uses it in the outer query with the associated password to confirm the password.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This is how I am interpreting the doc for LDAP_AUTH_METHOD=QUERY in sasauth.conf to work...&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp;# QUERY = Search for the user's name in a specified attribute to determine&lt;BR /&gt;&amp;nbsp; &amp;nbsp; # the user's DN, then BIND using that DN and the user's credentials.&lt;BR /&gt;&amp;nbsp; &amp;nbsp; # (Useful for large enterprises with multiple AD domains.)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;However, I have been unable to figure out how to set up sasauth.conf to connect using simple authentication (-x) and ldapuri (-H ldaps://....) and am hoping that this is my problem.&amp;nbsp; Can someone provide guidance on how to configure sasauth.conf to create its query using the form '-x -H ldaps://...:nnn' (or where it is discussed in the manuals) and where I can find the logging for this activity so that I can debug it?&amp;nbsp; I have been unable to find the logs for this anywhere.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks in advance, Dennis&lt;/P&gt;</description>
    <pubDate>Tue, 30 Jul 2019 14:43:33 GMT</pubDate>
    <dc:creator>doq</dc:creator>
    <dc:date>2019-07-30T14:43:33Z</dc:date>
    <item>
      <title>LDAP Authentication in Linux environment (for SAS Forecast Server)</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/LDAP-Authentication-in-Linux-environment-for-SAS-Forecast-Server/m-p/577723#M16861</link>
      <description>&lt;P&gt;Hi, I am implementing SAS Forecast Server on a Google Cloud Platform (GCP) Compute Instance/VM.&amp;nbsp; I am having problem configuring sasauth.conf to connect back to our on-prem LDAP server for password authentication.&amp;nbsp; One item of note is that the ldap server IP is actually the load balancer for our ldap servers.&amp;nbsp; Not sure if this is significant for my situation or not.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am able to perform an ldapsearch from the command line with an embedded fetch of the target DN as follows:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;ldapsearch -x -LLL \&lt;BR /&gt;&amp;nbsp;&amp;nbsp;-H ldaps://&amp;lt;ldaphost.domain.com&amp;gt;:636 \&lt;BR /&gt;&amp;nbsp;&amp;nbsp;-D "&lt;I&gt;$(ldapsearch -x -LLL \&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;-H ldaps://&amp;lt;ldaphost.domain.com&amp;gt;:636 \&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;-b 'o=,c=us' \&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;-s sub 'uid=&amp;lt;tgt_uid&amp;gt;' dn | grep dn | \&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;cut -d' ' -f2-)&lt;/I&gt;" \&lt;BR /&gt;&amp;nbsp;&amp;nbsp;-s sub "uid=&amp;lt;tgt_uid&amp;gt;" \&lt;BR /&gt;&amp;nbsp;&amp;nbsp;-b "o=,c=us" \&lt;BR /&gt;&amp;nbsp;&amp;nbsp;-w &amp;lt;user_psw&amp;gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Please note also that I have been unable to get an ldapsearch command to work using the form &lt;STRONG&gt;&lt;I&gt;'-h &amp;lt;ldaphost.domain.com&amp;gt; -p 636'&lt;/I&gt;&lt;/STRONG&gt; for the ldap host reference.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The above ldapsearch command fetches the DN first (and strips off the chars 'dn: '), and then uses it in the outer query with the associated password to confirm the password.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This is how I am interpreting the doc for LDAP_AUTH_METHOD=QUERY in sasauth.conf to work...&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp;# QUERY = Search for the user's name in a specified attribute to determine&lt;BR /&gt;&amp;nbsp; &amp;nbsp; # the user's DN, then BIND using that DN and the user's credentials.&lt;BR /&gt;&amp;nbsp; &amp;nbsp; # (Useful for large enterprises with multiple AD domains.)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;However, I have been unable to figure out how to set up sasauth.conf to connect using simple authentication (-x) and ldapuri (-H ldaps://....) and am hoping that this is my problem.&amp;nbsp; Can someone provide guidance on how to configure sasauth.conf to create its query using the form '-x -H ldaps://...:nnn' (or where it is discussed in the manuals) and where I can find the logging for this activity so that I can debug it?&amp;nbsp; I have been unable to find the logs for this anywhere.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks in advance, Dennis&lt;/P&gt;</description>
      <pubDate>Tue, 30 Jul 2019 14:43:33 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/LDAP-Authentication-in-Linux-environment-for-SAS-Forecast-Server/m-p/577723#M16861</guid>
      <dc:creator>doq</dc:creator>
      <dc:date>2019-07-30T14:43:33Z</dc:date>
    </item>
    <item>
      <title>Re: LDAP Authentication in Linux environment (for SAS Forecast Server)</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/LDAP-Authentication-in-Linux-environment-for-SAS-Forecast-Server/m-p/577797#M16870</link>
      <description>&lt;P&gt;&lt;a href="https://communities.sas.com/t5/user/viewprofilepage/user-id/197404"&gt;@doq&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The easiest way to configure LDAP authentication in sasauth.conf is to use BIND in LDAP_AUTH_METHOD. In that case, you are binding as the user and you do not need to have service account to search your users. As I said before, you need to make sure that your LDAP schema is UNIX enabled, meaning that your schema contains UID/GID for each user. sasauth-debug along with PROC PERMTEST can be used for debugging purposes, please see more details in a SAS note listed below:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="http://support.sas.com/kb/39/891.html" target="_self"&gt;http://support.sas.com/kb/39/891.html&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Also, I want to say, the easiest way to configure LDAP authentication is to do that on a system level. For example through SSSD and then use PAM authentication in SAS.&lt;/P&gt;</description>
      <pubDate>Tue, 30 Jul 2019 15:49:27 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/LDAP-Authentication-in-Linux-environment-for-SAS-Forecast-Server/m-p/577797#M16870</guid>
      <dc:creator>alexal</dc:creator>
      <dc:date>2019-07-30T15:49:27Z</dc:date>
    </item>
    <item>
      <title>Re: LDAP Authentication in Linux environment (for SAS Forecast Server)</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/LDAP-Authentication-in-Linux-environment-for-SAS-Forecast-Server/m-p/579106#M16907</link>
      <description>&lt;P&gt;I was able to accomplish what I needed to do via the PAM_EXEC module and the expose_authtok parameter.&amp;nbsp; This gave me the info I needed to perform my LDAP search directly without the overhead of SSSD.&lt;/P&gt;</description>
      <pubDate>Mon, 05 Aug 2019 11:41:51 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/LDAP-Authentication-in-Linux-environment-for-SAS-Forecast-Server/m-p/579106#M16907</guid>
      <dc:creator>doq</dc:creator>
      <dc:date>2019-08-05T11:41:51Z</dc:date>
    </item>
  </channel>
</rss>

