All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex AlexAlex <alex_unix20@yahoo.com>
To: autofs@linux.kernel.org
Subject: Ldap access
Date: Thu, 26 Jun 2008 15:36:36 -0700 (PDT)	[thread overview]
Message-ID: <292822.59991.qm@web32402.mail.mud.yahoo.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 592 bytes --]

Hi Gurus,
 
This is an interesting group regarding ldap issues.  So please let me know if you can help with the following;
I am currently testing the Ldap Directory Server version 6.3. I am able to use netgroup to control access for a particular node. This means when we build the client the /etc/passwd and /etc/shadow must have an entry for access control. ( +@<netgroup1> ). So, we have to make changes with regard to access both on the server and on the client.
 
Is there a way to manage all the changes on the server without ever touching the client?
 
Thanks…
-alex


      

[-- Attachment #1.2: Type: text/html, Size: 1731 bytes --]

[-- Attachment #2: Type: text/plain, Size: 140 bytes --]

_______________________________________________
autofs mailing list
autofs@linux.kernel.org
http://linux.kernel.org/mailman/listinfo/autofs

                 reply	other threads:[~2008-06-26 22:36 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=292822.59991.qm@web32402.mail.mud.yahoo.com \
    --to=alex_unix20@yahoo.com \
    --cc=autofs@linux.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.