Schema to add hostname property to accounts for pam_authz_search?
[Date Prev][Date Next] [Thread Prev][Thread Next]Schema to add hostname property to accounts for pam_authz_search?
- From: "J. L. Brewer" <jamie.brewer [at] grindwork.com>
- To: nss-pam-ldapd-users [at] lists.arthurdejong.org
- Subject: Schema to add hostname property to accounts for pam_authz_search?
- Date: Tue, 12 Apr 2011 15:04:48 -0700
Hi,
I'm examining what it would take to restrict user logins to given hostnames and add that capability to an existing database of users.
It requires a "host" attribute associated with the users ldap entry...ok, but schemas posixAccount and inetOrgPerson don't support that. The cosine schema has one but, I'm led to understand, it's not compatible with inetOrgPerson.
The PADL nss-ldap libpam-ldap package offers ldapns.schema for this purpose (http://old.nabble.com/Re:-Howto-get-the-%22host%22-attribute-for-pam_check_host_attr-of-pam_ldap--p9844227.html) (though exclude it from releases). Is this a sufficient solution or is there a more official, prefered solution for nss-pam-ldapd?
~Jamie Brewer
-- To unsubscribe send an email to nss-pam-ldapd-users-unsubscribe@lists.arthurdejong.org or see http://lists.arthurdejong.org/nss-pam-ldapd-users
- Schema to add hostname property to accounts for pam_authz_search?, J. L. Brewer
- Prev by Date: Re: Why use uniqueMember instead of member?
- Next by Date: Re: Schema to add hostname property to accounts for pam_authz_search?
- Previous by thread: Re: Why use uniqueMember instead of member?
- Next by thread: Re: Schema to add hostname property to accounts for pam_authz_search?