I am getting the following error message when trying to login to the client:
while verifying tgt
If I move the /etc/krb5.keytab out of /etc, it works fine. This is HP-UX v23
Does anyone have any ideas? (1 Reply)
I'm having troubles setting up a client(with Ubuntu 8.10) for a ldap+samba server. I can't authenticate through the client with gdm, the messages I have in /etc/auth.log at the client is
Dec 4 14:21:56 myuser-mydesktop gdm: nss_ldap: failed to bind to LDAP server ldap://192.168.0.1: Invalid... (5 Replies)
Good day
I am trying to configure Kerberos and LDAP authentication on AIX 5.3 with Windows 2003 R2 but something is not quite right.
When I ran kinit username I get a ticket and I can display it using klist.
When the user login I can see the ticket request on Windows 2003, but the user... (1 Reply)
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, FYI, I'm new in Solaris
I'm trying to use Kerberos on authenticating LDAP Client with the Active Directory on Windows Server 2003 on both Solaris 10 5/08 and Solaris 10 9/10 by referring to the pdf file kerberos_s10.pdf available at sun official site.
... (0 Replies)
I've configured an AIX 5.3 client to use our Windows AD for user authentication via Kerberos.
When I try to ssh to the server using the AD credentials, I eventually get access but not after getting prompted for a password 3 times (which doesn't work) followed by an accepted login on the 4th... (3 Replies)
I have been able to configure on an AIX 5.2 ldap.cfg so service starts correctly.
but when I try to log on with a windows user after entering the password login hangs and get no response.
I have set it up on Aix 5.3 with no problem but in Aix 5.2 I have not been able to log in.
ldap.cfg... (1 Reply)
Hi all,
I have installed samba 3.6.22 on AIX 7.1 and join a windows AD with success.
All seem to work fine, I have configured smb.conf, methods.cfg, kerberos, user .... the following command work fine wbinfo -u, wbinfo -g, wbinfo -i, wbinfo -s, wbinfo -S, lsuser, id...
The unique... (20 Replies)
Has anyone attempted to define GPO / HBAC policies in Windows Server 2012 that could be respected by Kerberos/LDAP on AIX?
I'm looking to associate servers to groups so that when a user part of a group tries to login to a host not associated with that group, it would be denied. This would allow... (3 Replies)
Discussion started by: Devyn
3 Replies
LEARN ABOUT CENTOS
pam_lastlog
PAM_LASTLOG(8) Linux-PAM Manual PAM_LASTLOG(8)NAME
pam_lastlog - PAM module to display date of last login and perform inactive account lock out
SYNOPSIS
pam_lastlog.so [debug] [silent] [never] [nodate] [nohost] [noterm] [nowtmp] [noupdate] [showfailed] [inactive=<days>]
DESCRIPTION
pam_lastlog is a PAM module to display a line of information about the last login of the user. In addition, the module maintains the
/var/log/lastlog file.
Some applications may perform this function themselves. In such cases, this module is not necessary.
If the module is called in the auth or account phase, the accounts that were not used recently enough will be disallowed to log in. The
check is not performed for the root account so the root is never locked out.
OPTIONS
debug
Print debug information.
silent
Don't inform the user about any previous login, just update the /var/log/lastlog file.
never
If the /var/log/lastlog file does not contain any old entries for the user, indicate that the user has never previously logged in with
a welcome message.
nodate
Don't display the date of the last login.
noterm
Don't display the terminal name on which the last login was attempted.
nohost
Don't indicate from which host the last login was attempted.
nowtmp
Don't update the wtmp entry.
noupdate
Don't update any file.
showfailed
Display number of failed login attempts and the date of the last failed attempt from btmp. The date is not displayed when nodate is
specified.
inactive=<days>
This option is specific for the auth or account phase. It specifies the number of days after the last login of the user when the user
will be locked out by the module. The default value is 90.
MODULE TYPES PROVIDED
The auth and account module type allows to lock out users which did not login recently enough. The session module type is provided for
displaying the information about the last login and/or updating the lastlog and wtmp files.
RETURN VALUES
PAM_SUCCESS
Everything was successful.
PAM_SERVICE_ERR
Internal service module error.
PAM_USER_UNKNOWN
User not known.
PAM_AUTH_ERR
User locked out in the auth or account phase due to inactivity.
PAM_IGNORE
There was an error during reading the lastlog file in the auth or account phase and thus inactivity of the user cannot be determined.
EXAMPLES
Add the following line to /etc/pam.d/login to display the last login time of an user:
session required pam_lastlog.so nowtmp
To reject the user if he did not login during the previous 50 days the following line can be used:
auth required pam_lastlog.so inactive=50
FILES
/var/log/lastlog
Lastlog logging file
SEE ALSO pam.conf(5), pam.d(5), pam(8)AUTHOR
pam_lastlog was written by Andrew G. Morgan <morgan@kernel.org>.
Inactive account lock out added by Toma Mraz <tm@t8m.info>.
Linux-PAM Manual 09/19/2013 PAM_LASTLOG(8)