| View previous topic :: View next topic |
| Author |
Message |
flipy
Apprentice
Joined: 15 Jul 2004
Posts: 236
|
 Posted: Tue Oct 31, 2006 12:06 pm Post subject: wireless auth ldap support |
 |
|
After setting up this PDC, I was thinking in a way to manage dhcp queries thru LDAP, but it's quite complicated.
My specific problem is that I need to manage wireless clients that connect thru an AP and authenticate them using LDAP.
But, since I'm still a newbie on this matter, I've not found any practical solution (I've heard something about DHCP+LDAP patch, but don't know)
Does anyone has got this same problem and configured it successfully?
Thanks |
|
| Back to top |
|
 |
korda
n00b
Joined: 14 Nov 2004
Posts: 11
Location: Australia
|
| Posted: Wed Dec 27, 2006 1:30 pm Post subject: Re: wireless auth ldap support |
|
|
| flipy wrote: | After setting up this PDC, I was thinking in a way to manage dhcp queries thru LDAP, but it's quite complicated.
My specific problem is that I need to manage wireless clients that connect thru an AP and authenticate them using LDAP.
But, since I'm still a newbie on this matter, I've not found any practical solution (I've heard something about DHCP+LDAP patch, but don't know)
Does anyone has got this same problem and configured it successfully?
Thanks |
FreeRADIUS might help you out there, I use it for wireless clients on our PDC as the wireless AP we use (some dlink thing, it's 150km away from me atm) can talk to a RADIUS server for authentication.
Also in the new year I'll attempt to use Po0ky's HOWTO to convert our current samba+gentoo PDC to use ldap for authentication, right now we use samba for wired workstation logins and unix passwords for personal laptop logins via freeradius and SSH shell access. We use unix/samba password synchronisation to reconcile the two.
It's quite bad, openldap seemed too hard to set up at the time but I think this howto will help out immensely in standardising shell, freeradius wireless users and samba workstation users. |
|
| Back to top |
|
|
Jeremy_Z
l33t
Joined: 05 Apr 2004
Posts: 671
Location: Shanghai
|
| Posted: Sun Jan 21, 2007 2:25 pm Post subject: |
|
|
Hi, nice guide 
One thing stupid happened to me, samba would not start after configuring it according to the guide.
I had to skip that and run the populate, after that it could start fine.
_________________
"Because two groups of consumers drive the absolute high end of home computing: the gamers and the porn surfers." /.
My gentoo projects, Kelogviewer and a QT4 gui for etc-proposals |
|
| Back to top |
|
|
dwalexuk
n00b
Joined: 09 Mar 2004
Posts: 41
|
| Posted: Fri Mar 09, 2007 9:59 am Post subject: smbk5pwd |
|
|
I compiled smbk5pwd following instructions on talk page, and it's loaded ok, but is doesn't synchronise passwords. (when you change password using passwd)
Is any way to debug this? I use loglevel 2304 in slapd.conf but I still don't have any clues. |
|
| Back to top |
|
|
nianderson
Guru
Joined: 06 May 2003
Posts: 369
Location: Lawrence, KS
|
| Posted: Sat Apr 07, 2007 5:08 am Post subject: |
|
|
I have a working samba + ldap pdc that I inherited. I am wanting to add a standalone file server to the mix. I want the file server to just auth against my ldap server. Im having problems figuring out what I actually need to configure.
Do I only need to do the Samba section and not the nsswitch etc ... And in the Samba section leave out
Netlogon shares, Profiles, and Adding machine accounts? |
|
| Back to top |
|
|
GD
Tux's lil' helper
Joined: 11 May 2005
Posts: 138
Location: Greece
|
| Posted: Sat May 05, 2007 11:28 pm Post subject: |
|
|
hello....
thanks for the how-to... it seems to be working apart from a few points:
NOTE: I used the 5/05/2007 notes about not editing any pam.d files... I just added ldap to /etc/nsswitch.conf
NOTE2: I'm running gentoo-hardened although I have not configured grsec and stuff so far... (kernel support is enabled though...)
when doing a getent passwd | grep 0:0 this is what I get:
| Code: |
gaea log # getent passwd | grep 0:0
request done: ld 0x523f30 msgid 1
request done: ld 0x523f30 msgid 2
request done: ld 0x523f30 msgid 3
root:x:0:0:root:/root:/bin/bash
root:x:0:0:Netbios Domain Administrator:/home/root:/bin/false
|
Is this OK?
But the most important thing is that the testuser test doesn't work... I've successfully added the user user smbldap-tools, but for some reason authentication fails. Here's the output in /var/log/auth.log:
| Code: | May 6 01:03:16 gaea sshd[2650]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=gaea.gaza.net user=testuser
May 6 01:03:19 gaea sshd[2645]: error: PAM: Authentication failure for testuser from gaea.gaza.net
May 6 01:04:25 gaea sshd[2651]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=gaea.gaza.net user=testuser
May 6 01:04:27 gaea sshd[2645]: error: PAM: Authentication failure for testuser from gaea.gaza.net
May 6 01:04:31 gaea sshd[2665]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=gaea.gaza.net user=testuser
May 6 01:04:32 gaea sshd[2660]: error: PAM: Authentication failure for testuser from gaea.gaza.net
|
it seems the ldap server can't be contacted for some reason... however all the other tests described in the how-to seem to work fine... here's my /etc/ldap.conf:
| Quote: | # @(#)$Id: ldap.conf,v 2.47 2006/05/15 08:13:44 lukeh Exp $
#
# This is the configuration file for the LDAP nameservice
# switch library and the LDAP PAM module.
#
# PADL Software
# http://www.padl.com
#
# Your LDAP server. Must be resolvable without using LDAP.
# Multiple hosts may be specified, each separated by a
# space. How long nss_ldap takes to failover depends on
# whether your LDAP client library supports configurable
# network or connect timeouts (see bind_timelimit).
host 127.0.0.1
# The distinguished name of the search base.
base dc=GAZA,dc=NET
# Another way to specify your LDAP server is to provide an
# uri with the server name. This allows to use
# Unix Domain Sockets to connect to a local LDAP Server.
#uri ldap://127.0.0.1/
#uri ldaps://127.0.0.1/
#uri ldapi://%2fvar%2frun%2fldapi_sock/
# Note: %2f encodes the '/' used as directory separator
# The LDAP version to use (defaults to 3
# if supported by client library)
#ldap_version 3
# The distinguished name to bind to the server with.
# Optional: default is to bind anonymously.
#binddn cn=Manager,dc=GAZA,dc=NET
# The credentials to bind with.
# Optional: default is no credential.
#bindpw secret
# The distinguished name to bind to the server with
# if the effective user ID is root. Password is
# stored in /etc/ldap.secret (mode 600)
rootbinddn cn=Manager,dc=GAZA,dc=NET
# The port.
# Optional: default is 389.
#port 389
# The search scope.
scope sub
#scope one
#scope base
# Search timelimit
#timelimit 30
# Bind/connect timelimit
#bind_timelimit 30
# Reconnect policy:
# hard_open: reconnect to DSA with exponential backoff if
# opening connection failed
# hard_init: reconnect to DSA with exponential backoff if
# initializing connection failed
# hard: alias for hard_open
# soft: return immediately on server failure
bind_policy soft
# Connection policy:
# persist: DSA connections are kept open (default)
# oneshot: DSA connections destroyed after request
#nss_connect_policy persist
# Idle timelimit; client will close connections
# (nss_ldap only) if the server has not been contacted
# for the number of seconds specified below.
#idle_timelimit 3600
# Use paged rseults
#nss_paged_results yes
# Pagesize: when paged results enable, used to set the
# pagesize to a custom value
#pagesize 1000
# Filter to AND with uid=%s
pam_filter objectclass=posixAccount
# The user ID attribute (defaults to uid)
pam_login_attribute uid
# Search the root DSE for the password policy (works
# with Netscape Directory Server)
#pam_lookup_policy yes
# Check the 'host' attribute for access control
# Default is no; if set to yes, and user has no
# value for the host attribute, and pam_ldap is
# configured for account management (authorization)
# then the user will not be allowed to login.
#pam_check_host_attr yes
# Check the 'authorizedService' attribute for access
# control
# Default is no; if set to yes, and the user has no
# value for the authorizedService attribute, and
# pam_ldap is configured for account management
# (authorization) then the user will not be allowed
# to login.
#pam_check_service_attr yes
# Group to enforce membership of
#pam_groupdn cn=PAM,ou=Groups,dc=padl,dc=com
# Group member attribute
#pam_member_attribute uniquemember
# Specify a minium or maximum UID number allowed
#pam_min_uid 0
#pam_max_uid 0
# Template login attribute, default template user
# (can be overriden by value of former attribute
# in user's entry)
#pam_login_attribute userPrincipalName
#pam_template_login_attribute uid
#pam_template_login nobody
# HEADS UP: the pam_crypt, pam_nds_passwd,
# and pam_ad_passwd options are no
# longer supported.
#
# Do not hash the password at all; presume
# the directory server will do it, if
# necessary. This is the default.
#pam_password clear
# Hash password locally; required for University of
# Michigan LDAP server, and works with Netscape
# Directory Server if you're using the UNIX-Crypt
# hash mechanism and not using the NT Synchronization
# service.
#pam_password crypt
# Remove old password first, then update in
# cleartext. Necessary for use with Novell
# Directory Services (NDS)
#pam_password nds
# RACF is an alias for the above. For use with
# IBM RACF
#pam_password racf
# Update Active Directory password, by
# creating Unicode password and updating
# unicodePwd attribute.
#pam_password ad
# Use the OpenLDAP password change
# extended operation to update the password.
#pam_password exop
pam_password md5
# Redirect users to a URL or somesuch on password
# changes.
#pam_password_prohibit_message Please visit http://internal to change your password.
# Use backlinks for answering initgroups()
#nss_initgroups backlink
# Enable support for RFC2307bis (distinguished names in group
# members)
#nss_schema rfc2307bis
# RFC2307bis naming contexts
# Syntax:
# nss_base_XXX base?scope?filter
# where scope is {base,one,sub}
# and filter is a filter to be &'d with the
# default filter.
# You can omit the suffix eg:
# nss_base_passwd ou=People,
# to append the default base DN but this
# may incur a small performance impact.
nss_base_passwd ou=Computers,dc=GAZA,dc=NET?sub
nss_base_passwd ou=Users,dc=GAZA,dc=NET?sub
nss_base_shadow ou=Users,dc=GAZA,dc=NET?sub
nss_base_group ou=Group,dc=GAZA,dc=NET?one
#nss_base_hosts ou=Hosts,dc=padl,dc=com?one
#nss_base_services ou=Services,dc=padl,dc=com?one
#nss_base_networks ou=Networks,dc=padl,dc=com?one
#nss_base_protocols ou=Protocols,dc=padl,dc=com?one
#nss_base_rpc ou=Rpc,dc=padl,dc=com?one
#nss_base_ethers ou=Ethers,dc=padl,dc=com?one
#nss_base_netmasks ou=Networks,dc=padl,dc=com?ne
#nss_base_bootparams ou=Ethers,dc=padl,dc=com?one
#nss_base_aliases ou=Aliases,dc=padl,dc=com?one
#nss_base_netgroup ou=Netgroup,dc=padl,dc=com?one
# attribute/objectclass mapping
# Syntax:
#nss_map_attribute rfc2307attribute mapped_attribute
#nss_map_objectclass rfc2307objectclass mapped_objectclass
# configure --enable-nds is no longer supported.
# NDS mappings
#nss_map_attribute uniqueMember member
# Services for UNIX 3.5 mappings
#nss_map_objectclass posixAccount User
#nss_map_objectclass shadowAccount User
#nss_map_attribute uid msSFU30Name
#nss_map_attribute uniqueMember msSFU30PosixMember
#nss_map_attribute userPassword msSFU30Password
#nss_map_attribute homeDirectory msSFU30HomeDirectory
#nss_map_attribute homeDirectory msSFUHomeDirectory
#nss_map_objectclass posixGroup Group
#pam_login_attribute msSFU30Name
#pam_filter objectclass=User
#pam_password ad
# configure --enable-mssfu-schema is no longer supported.
# Services for UNIX 2.0 mappings
#nss_map_objectclass posixAccount User
#nss_map_objectclass shadowAccount user
#nss_map_attribute uid msSFUName
#nss_map_attribute uniqueMember posixMember
#nss_map_attribute userPassword msSFUPassword
#nss_map_attribute homeDirectory msSFUHomeDirectory
#nss_map_attribute shadowLastChange pwdLastSet
#nss_map_objectclass posixGroup Group
#nss_map_attribute cn msSFUName
#pam_login_attribute msSFUName
#pam_filter objectclass=User
#pam_password ad
# RFC 2307 (AD) mappings
#nss_map_objectclass posixAccount user
#nss_map_objectclass shadowAccount user
#nss_map_attribute uid sAMAccountName
#nss_map_attribute homeDirectory unixHomeDirectory
#nss_map_attribute shadowLastChange pwdLastSet
#nss_map_objectclass posixGroup group
#nss_map_attribute uniqueMember member
#pam_login_attribute sAMAccountName
#pam_filter objectclass=User
#pam_password ad
# configure --enable-authpassword is no longer supported
# AuthPassword mappings
#nss_map_attribute userPassword authPassword
# AIX SecureWay mappings
#nss_map_objectclass posixAccount aixAccount
#nss_base_passwd ou=aixaccount,?one
#nss_map_attribute uid userName
#nss_map_attribute gidNumber gid
#nss_map_attribute uidNumber uid
#nss_map_attribute userPassword passwordChar
#nss_map_objectclass posixGroup aixAccessGroup
#nss_base_group ou=aixgroup,?one
#nss_map_attribute cn groupName
#nss_map_attribute uniqueMember member
#pam_login_attribute userName
#pam_filter objectclass=aixAccount
#pam_password clear
# For pre-RFC2307bis automount schema
#nss_map_objectclass automountMap nisMap
#nss_map_attribute automountMapName nisMapName
#nss_map_objectclass automount nisObject
#nss_map_attribute automountKey cn
#nss_map_attribute automountInformation nisMapEntry
# Netscape SDK LDAPS
#ssl on
ssl no
# Netscape SDK SSL options
#sslpath /etc/ssl/certs
# OpenLDAP SSL mechanism
# start_tls mechanism uses the normal LDAP port, LDAPS typically 636
#ssl start_tls
###ssl on
# Gentoo note: Don't use 'ssl on' in 249/250. They are broken in some cases! Use start_tls instead.
# OpenLDAP SSL options
# Require and verify server certificate (yes/no)
# Default is to use libldap's default behavior, which can be configured in
# /etc/openldap/ldap.conf using the TLS_REQCERT setting. The default for
# OpenLDAP 2.0 and earlier is "no", for 2.1 and later is "yes".
#tls_checkpeer yes
# CA certificates for server certificate verification
# At least one of these are required if tls_checkpeer is "yes"
#tls_cacertfile /etc/ssl/ca.cert
#tls_cacertdir /etc/ssl/certs
# Seed the PRNG if /dev/urandom is not provided
#tls_randfile /var/run/egd-pool
# SSL cipher suite
# See man ciphers for syntax
#tls_ciphers TLSv1
# Client certificate and key
# Use these, if your server requires client authentication.
#tls_cert
#tls_key
# Disable SASL security layers. This is needed for AD.
#sasl_secprops maxssf=0
# Override the default Kerberos ticket cache location.
#krb5_ccname FILE:/etc/.ldapcache
# Timeout behavior
# Upstream nss_ldap hard-codes these values:
#nss_reconnect_tries 5 # number of times to double the sleep time
#nss_reconnect_sleeptime 4 # initial sleep value
#nss_reconnect_maxsleeptime 64 # max sleep value to cap at
#nss_reconnect_maxconntries 2 # how many tries before sleeping
# This leads to a delay of 124 seconds (4+8+16+32+64=124) per lookup if the
# server is not available.
# For Gentoo's distribution of nss_ldap, as of 250-r1, we use these values
# (The hardwired constants in the code are changed to them as well):
nss_reconnect_tries 4 # number of times to double the sleep time
nss_reconnect_sleeptime 1 # initial sleep value
nss_reconnect_maxsleeptime 16 # max sleep value to cap at
nss_reconnect_maxconntries 2 # how many tries before sleeping
# This leads to a delay of 15 seconds (1+2+4+8=15)
# If you are impatient, and know your LDAP server is reliable, fast or local,
# you may wish to use these values instead:
#nss_reconnect_tries 1 # number of times to double the sleep time
#nss_reconnect_sleeptime 1 # initial sleep value
#nss_reconnect_maxsleeptime 1 # max sleep value to cap at
#nss_reconnect_maxconntries 3 # how many tries before sleeping
# This leads to a delay of 1 second.
debug 256
logdir /var/log/nss_ldap
|
I've also created a /etc/ldap.secret file which contains the Manager password in cleartext... Any ideas on what might be wrong here? Any ways to do further debugging to find out where the problem is lying?
Thanks in advance...
george |
|
| Back to top |
|
|
GD
Tux's lil' helper
Joined: 11 May 2005
Posts: 138
Location: Greece
|
| Posted: Sun May 06, 2007 1:34 am Post subject: |
|
|
| solved... I edited the /etc/pam.d/system.auth file anyway... any idea why this comment about skipping that section is present in the wiki? |
|
| Back to top |
|
|
KingOfSka
n00b
Joined: 07 Jun 2005
Posts: 11
|
| Posted: Sun Jul 15, 2007 6:45 pm Post subject: |
|
|
i got ssh login of ldap users , and share browsing fully working, but when i try to join the domain from a windows XP client, i get "A system device is disconnected" erorr and can't login.
on my gentoo box , in the log file of samba, i see
| Code: |
[2007/07/15 04:45:56, 1] rpc_server/srv_netlog_nt.c:_net_sam_logon_internal(1004)
_net_sam_logon: user TEST_DOMAIN\testusera has user sid S-1-5-21-4205727931-4131263253-1851132061-3002
but group sid S-1-5-21-1474600641-904944587-3008827518-513.
The conflicting domain portions are not supported for NETLOGON calls
|
also in /var/log/samba/log.smbd i found
| Code: |
[2007/07/15 04:24:00, 1] passdb/pdb_interface.c:pdb_default_uid_to_rid(1233)
Could not peek rid out of sid S-1-5-21-4205727931-4131263253-1851132061-500
|
i installed phpldapadmin to try to manage this records but don't know what to do, i googled around and found of removing the groups and recreating them, but i've already done and didn't get any results |
|
| Back to top |
|
|
Falador
n00b
Joined: 18 Jan 2004
Posts: 60
|
| Posted: Sun Jul 15, 2007 9:01 pm Post subject: |
|
|
KingOfSka. I'm 99.9% sure your SIDs should match, apart from the last set of numbers.
| Code: | [2007/07/15 04:45:56, 1] rpc_server/srv_netlog_nt.c:_net_sam_logon_internal(1004)
_net_sam_logon: user TEST_DOMAIN\testusera has user sid S-1-5-21-4205727931-4131263253-1851132061-3002
but group sid S-1-5-21-1474600641-904944587-3008827518-513.
The conflicting domain portions are not supported for NETLOGON calls |
Looking at this 'testusera' has a uid of 3002 and is a member of group id 513 (last set of SID digits). The rest should match, yours doesn't. |
|
| Back to top |
|
|
KingOfSka
n00b
Joined: 07 Jun 2005
Posts: 11
|
| Posted: Mon Jul 16, 2007 9:39 am Post subject: |
|
|
so i should try to change the ldap SID entry for my testuser and see if it works ? i'm taking a new look at config files and do some test during this day..
edit: solved all problems, don't know how because from some problem i had to reinstall all the stuff back and now it's fully working  |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Networking & Security
