HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: LDAPux Filters
Operating System - HP-UX
1827487
Members
2194
Online
109965
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- 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
11-11-2008 07:40 AM
11-11-2008 07:40 AM
LDAPux Filters
Is there a method for supplying machine specific filters for the password base search without creating ldapux profiles for each machine?
We are using LDAPux on our HP clients and nss_ldap on our Linux clients. Both sets of clients are retrieving userid and group information from Windows 2003 AD.
On our Linux clients it is possible to alter the machines search by specifing a filter on the nss_base_passwd field similar to:
nss_base_passwd dc=abc,dc=net?sub?MemberOf=CN=machine1,OU=groups,DC=abc,DC=net
This will allow only users with group of CN-machine1 to be visable to machine1. The same command can be repeated for machine2..machineN.
Since the ldapuxprofile is shared among all hpclients. It does not appear as though we can use this type of filter, unless we create individual profiles for each machine.
Is there a method or overriding the profile global default filter on a machine by machine bases? or some other method of reducing the number of userid visable via the pwget type commands?
We are using LDAPux on our HP clients and nss_ldap on our Linux clients. Both sets of clients are retrieving userid and group information from Windows 2003 AD.
On our Linux clients it is possible to alter the machines search by specifing a filter on the nss_base_passwd field similar to:
nss_base_passwd dc=abc,dc=net?sub?MemberOf=CN=machine1,OU=groups,DC=abc,DC=net
This will allow only users with group of CN-machine1 to be visable to machine1. The same command can be repeated for machine2..machineN.
Since the ldapuxprofile is shared among all hpclients. It does not appear as though we can use this type of filter, unless we create individual profiles for each machine.
Is there a method or overriding the profile global default filter on a machine by machine bases? or some other method of reducing the number of userid visable via the pwget type commands?
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-17-2008 11:14 AM
11-17-2008 11:14 AM
Re: LDAPux Filters
To filter out which users show up on a host (are visible through NSS), you would need a unique profile for each host.
However, if your goal is to allow logins only from a select set of users, then you can do that with pam_authz (part of LDAP-UX). You can define which groups of users are allowed to login to a host based on a number of criteria, such as the one above (filtering based on a MemberOf attribute).
Refer to "LDAP-UX Client Services B.04.15 Administrator's Guide (edition 9)" at http://docs.hp.com/en/J4269-90083/J4269-90083.pdf. Refer to chapter 5, subsection "PAM_AUTHZ Login Authorization".
You would create the /etc/opt/ldapux/pam_authz.policy and place your filtering rule in there. With ADS, there are two ways to achive the above restriction:
allow:ldap_group:CN=machine1,OU=groups,DC=abc,DC=net
or
allow:ldap_filter:(MemberOf=CN=machine1,OU=groups,DC=abc,DC=net)
Hope that helps,
Bob
However, if your goal is to allow logins only from a select set of users, then you can do that with pam_authz (part of LDAP-UX). You can define which groups of users are allowed to login to a host based on a number of criteria, such as the one above (filtering based on a MemberOf attribute).
Refer to "LDAP-UX Client Services B.04.15 Administrator's Guide (edition 9)" at http://docs.hp.com/en/J4269-90083/J4269-90083.pdf. Refer to chapter 5, subsection "PAM_AUTHZ Login Authorization".
You would create the /etc/opt/ldapux/pam_authz.policy and place your filtering rule in there. With ADS, there are two ways to achive the above restriction:
allow:ldap_group:CN=machine1,OU=groups,DC=abc,DC=net
or
allow:ldap_filter:(MemberOf=CN=machine1,OU=groups,DC=abc,DC=net)
Hope that helps,
Bob
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Support
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP