× Welcome to the Centrify Community! We are rolling out product name changes — click here to learn more.

adbindproxy 5.4.0.294 compatibility with samba 4.6.4

Showing results for 
Search instead for 
Do you mean 
Reply
Participant II
Posts: 3
Registered: ‎10-06-2016
#1 of 5 392
Accepted Solution

adbindproxy 5.4.0.294 compatibility with samba 4.6.4

Are there any known compatibility issues with the adbindproxy 5.4.0.294 and samba 4.6.4. I downloaded the samba from IBM DeveloperWorks and ran throught the centrify procedure documented to integrate samba. The services are started but I can't get authentication to work. Using the centrify generated smb.conf file with the samba resource samba-test I am prompting for username and password. Thanks!

 

 

Kiana Havior

Centrify
Posts: 6
Registered: ‎03-13-2015
#2 of 5 352

Re: adbindproxy 5.4.0.294 compatibility with samba 4.6.4

Thank you for posting in Centrify Community.

A quick answer to your question about compatibility is that adbindproxy 5.4.0 must be ran under Centrify DirectControl (CDC) 5.4.0+.
May I know what is adclient version running on the Samba server?  Verified by adinfo -v

If you have CDC 5.4.0+ running then we need to check for other basic information first:

Has the setup been done in following sequence

1. Setup Samba
2. Setup CDC with a compatible version - i.e. CDC 5.4.0+
3. Setup adbindproxy package (5.4.0)
4. Running adbindproxy.pl to integrate Samba with Centrify - this should also including starting the services:

e.g.

nmbd (pid  35360) is running...
winbindd (pid  35368) is running...
adbindd (pid 35377) is running...
smbd (pid  35390) is running...

> If services are not running, please try to restart and confirm.

Could you also help to get the output of following commands from Samba server:

wbinfo -p

wbinfo -t

adquery user -A <username>

dzinfo -A <username>

Regards,
Alan

Participant II
Posts: 3
Registered: ‎10-06-2016
#3 of 5 333

Re: adbindproxy 5.4.0.294 compatibility with samba 4.6.4

Here is the iformation you requested. The software for CDC and adbind were already installed prior to me installing samba, then I ran the adbindproxy.pl and all services started. What would cause the wbinfo -p and -t to fail?

 

adifno -v

adinfo (CentrifyDC 5.4.1-455)

 

wbinfo -p

Ping to winbindd failed
could not ping winbindd!

 

wbifno -t

could not obtain winbind interface details: WBC_ERR_WINBIND_NOT_AVAILABLE
could not obtain winbind domain name!
checking the trust secret for domain  via RPC calls failed
failed to call wbcCheckTrustCredentials: WBC_ERR_WINBIND_NOT_AVAILABLE
Could not check secret

 

adquery user -A username

unixname:username
uid:xxxxxxxxx
gid:xxxxxxxxxx
gecos:Last, First
home:/home/username
shell:/usr/bin/ksh
auditLevel:AuditIfPossible

(didn't copy all data)

 

dzinfo -A username

User: username
Forced into restricted environment: No
Centrify MFA Service authentication: Supported

  Role Name        Description           Avail Restricted Env  Effective             Expires
              Available Hours                                    Visible
  ---------------  --------------------  ----- --------------  --------------------  --------
------------  -------------------------------------------------  -------

(didn't copy all info)

Centrify
Posts: 6
Registered: ‎03-13-2015
#4 of 5 320

Re: adbindproxy 5.4.0.294 compatibility with samba 4.6.4

Hi Kiana,

 

The winbind socket is not located correctly in adbindproxy.pl.  Could you follow below KB to find the correct path of winbind socket path and apply it again by re-running the adbindproxy.pl?

 

https://centrify.force.com/support/Article/KB-7411-Samba-Troubleshooting-Finding-the-location-of-win...

 

Regards,

Alan

Participant II
Posts: 3
Registered: ‎10-06-2016
#5 of 5 275

Re: adbindproxy 5.4.0.294 compatibility with samba 4.6.4

Thank you so much. That KB led me to the correct winbind socket path. I am now able to authenticate.