- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- LDAP-UX + 389-ds
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-13-2011 01:44 AM
тАО06-13-2011 01:44 AM
LDAP-UX + 389-ds
I've see that the following message appears in syslog : "sshd[29721]: PAM_AUTHZ: query daemon return failure status 7"
Any Ideas?? Thank in advance!
- Tags:
- LDAP
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-15-2012 12:04 PM
тАО11-15-2012 12:04 PM
Re: LDAP-UX + 389-ds
I know this thread is old, but I thought I would share my experience so far. I too have not been able to get the check_rhds_policy to work with pam_authz. I setup the proxy user and set the aci's specified in the ldaup 5.01 admin guide. In the end, the only way I could get the password policies to work is by adding filters to pam_authz.policy.
required:ldap_filter:(passwordexpirationtime>=$[TIMEOFTHEDAY])
PAM_PERM_DENIED:ldap_filter:(nsaccountlock=true)
PAM_MAXTRIES:ldap_filter:(&(accountunlocktime=19700101000000Z)(passwordretrycount=3))
This is about all you need to make sure users cannot login even though the directory shows thes users paswords expired, or account locked/inactive.
I hope this helps someone.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-20-2012 01:23 PM
тАО12-20-2012 01:23 PM
Re: LDAP-UX + 389-ds
I need to revise this. I ran into issues. This has worked for me.
PAM_NEW_AUTHTOK_REQD:ldap_filter:(passwordexpirationtime<=$[TIMEOFTHEDAY])
PAM_ACCT_EXPIRED:ldap_filter:(nsaccountlock=true)
PAM_ACCT_EXPIRED:ldap_filter:(&(accountunlocktime=19700101000000Z)(passwordretrycount=3))
I am still trying to figure out how to get the status:rhds:check_rdhs_policy line to work properly.