Hi everyone,
I wonder if anyone ever came across the idea of unifying AD and Linux user accounts
We have a Linux machine with 'samba' 'winbind' service configured to let Windows AD users to logon locally using their AD accounts and passwords.
I can use 'su' to get to the local user privilege... (0 Replies)
Hi all.
I'm having real trouble authenticating users against active directory for my SCO UnixWare 7.1.4 box running samba 3.0.24 (installed via Maintenance pack 4). I can list AD users/groups (after overcoming several hiccups) with wbinfo -g / wbinfo -u. I can use id to get a view an ad user ie:... (0 Replies)
Hello, I asked this question in the AIX subforum but never received an answer, probably because the AIX forum is not that heavily trafficked. Anyway, here it is..
I have never had any issues like this when compiling applications from source. When I try to compile samba-3.5.0pre2, configure runs... (9 Replies)
Hi,
I have recently taken control of a number of RHEL5.3 servers that have samba shares setup on them and are authenticating using pam and winbind. My issue is that any user that has an active directory account can currently log in to the linux boxes using their ad credentials. I need to... (0 Replies)
Hi,
We now have a Samba or Winbind issue. The Linux client under RHEL6 can not get Windows' AD sub-domain info. See the following output please. The main domain 'Global' is shown online, but the sub-domain 'Europe' and 'Asia' are shown offline although they are online.
Commands 'wbinfo -u' and... (0 Replies)
I configured AIX5.3 to use kerberos and winbind so user can login and authenticate via AD. I was able to join my AIX server to domain and can execute wbinfo -u/g. However when I login, It says unknown user. I already edit /etc/secuirty/user and then method.cfg.
On the log.winbindd it says
... (0 Replies)
The situation: i have a AD server with samba4,all clients
ssh-kerberos works fine,except hpux :p wich works
only for few days..then i must re-export(sic!) the keys with
samba-tool domain exportkeytab 11.keytab --principal=host/hpux.fqdn
Why after few days ssh return error "server not found... (1 Reply)
I have joined an AIX 7.1 into a 2012 AD domain sucesfully.
I can get ouput from wbinfo -u but when I try to access a share I get the following error :
check_ntlm_password: Authentication for user -> FAILED with
error NT_STATUS_NO_SUCH_USER
I have found that I'm missing... (0 Replies)
I have installed following packages from perzl
samba-winbind-clients-3.6.22-1
samba-client-3.6.22-1
samba-domainjoin-gui-3.6.22-1
samba-winbind-devel-3.6.22-1
samba-3.6.22-1
samba-common-3.6.22-1
samba-winbind-krb5-locator-3.6.22-1
samba-doc-3.6.22-1
samba-swat-3.6.22-1... (7 Replies)
I am running AIX 7.1 and currently we have samba 3.6.25 installed on the server. As it stands some AIX folders are shared that can be accessed by certain Windows users.
The problem is that since Windows 10 the guest feature no longer works so users have to manually type in their Windows login/pwd... (14 Replies)
Discussion started by: linuxsnake
14 Replies
LEARN ABOUT HPUX
pam_user.conf
pam_user.conf(4) Kernel Interfaces Manual pam_user.conf(4)NAME
pam_user.conf - user configuration file for pluggable authentication modules
SYNOPSIS DESCRIPTION
is the user configuration file for the Pluggable Authentication Module architecture, or PAM. It is not designed to replace the PAM system
configuration file, For PAM to work properly, is mandatory (see pam.conf(4)). is optional. It is used only when a user basis configura-
tion is needed. It mainly specifies options to be used by service modules on a user basis.
The options defined in indicate the default for users who are not configured in or if the module type is not configured for some users.
For the configuration in to take effect, needs to configure service module (see pam.conf(4)).
Simplified pam_user.conf Configuration File
The file contains a listing of login names. Each login name is paired with a corresponding service module with or without options speci-
fied. Each entry has the following format:
login_name module_type module_path options
Below is an example of the configuration file.
tom auth /usr/lib/security/$ISA/libpam_unix.so.1 debug use_psd
tom auth /usr/lib/security/$ISA/libpam_dce.so.1 use_first_pass
tom account /usr/lib/security/$ISA/libpam_unix.so.1 use_psd
tom account /usr/lib/security/$ISA/libpam_dce.so.1 try_first_pass
susan auth /usr/lib/security/$ISA/libpam_unix.so.1
susan auth /usr/lib/security/$ISA/libpam_dce.so.1 try_first_pass
The login_name denotes the login name of a user (for example, For detailed information on module_type, module_path, and options, see
pam.conf(4).
The first entry indicates that when the UNIX authentication is invoked for the options and will be used. The second entry indicates that
when the DCE authentication is invoked for the option will be used. The module type is not configured for therefore, the options will take
effect. For those users who are not configured, the options apply.
Notes
If an error is found in an entry due to invalid login_name or module_type, then the entry is ignored. If there are no valid entries for
the given module_type, the PAM framework ignores and reads the configuration in
EXAMPLES
The following is a sample configuration file. Lines that begin with the symbol are treated as comments, and therefore ignored.
#
# PAM user configuration
#
# Authentication management
john auth /usr/lib/security/$ISA/libpam_unix.so.1
john auth /usr/lib/security/$ISA/libpam_inhouse.so.1 try_first_pass
david auth /usr/lib/security/$ISA/libpam_unix.so.1 use_psd
david auth /usr/lib/security/$ISA/libpam_inhouse.so.1 try_first_pass
susan auth /usr/lib/security/$ISA/libpam_unix.so.1 use_psd
susan auth /usr/lib/security/$ISA/libpam_inhouse.so.1 try_first_pass
# Password management
john password /usr/lib/security/$ISA/libpam_unix.so.1
david password /usr/lib/security/$ISA/libpam_unix.so.1 use_psd
susan password /usr/lib/security/$ISA/libpam_unix.so.1 use_psd
SEE ALSO pam(3), pam.conf(4).
pam_user.conf(4)