From: "Alexander A. Filippov" <a.filippov@yadro.com>
To: Paul Fertser <fercerpav@gmail.com>
Cc: openbmc@lists.ozlabs.org
Subject: Re: LDAP groups and roles mapping
Date: Mon, 10 Jan 2022 18:56:32 +0300 [thread overview]
Message-ID: <YdxXMBloqYjk8Zy8@nbwork.lan> (raw)
In-Reply-To: <YdxFQl9Opddem7O5@home.paul.comp>
On Mon, Jan 10, 2022 at 05:40:02PM +0300, Paul Fertser wrote:
> Hi,
>
> On Mon, Jan 10, 2022 at 05:12:46PM +0300, Alexander A. Filippov wrote:
> > Our customers want LDAP groups and roles mapping working not only by primary
> > group, but also by the membership in one of these groups.
> > And this requirement seems to me reasonable.
>
> A sidenote: windows active directory admins might also want you to
> take nested groups into consideration. I suggest you check with the
> customers if that's the case or not.
>
Yes, it looks like a problem.
I'm afraid that the recursive queries will execute too long and PAM will give
rejection by timeout.
But `phosphor-user-manager` allows to create mappings of several LDAP groups
into one role and thus, I suppose, we can claim that we don't support the nested
groups.
> AFAIK there's no standard way to do that (other than recursively walk
> through the group membership) but microsoft has
> LDAP_MATCHING_RULE_IN_CHAIN OID:
> https://docs.microsoft.com/en-us/windows/win32/adsi/search-filter-syntax
>
> --
> Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software!
> mailto:fercerpav@gmail.com
--
Alexander
next prev parent reply other threads:[~2022-01-10 15:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-10 14:12 LDAP groups and roles mapping Alexander A. Filippov
2022-01-10 14:40 ` Paul Fertser
2022-01-10 15:56 ` Alexander A. Filippov [this message]
2022-01-10 21:00 ` Paul Fertser
2022-02-10 10:24 ` Alexander A. Filippov
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=YdxXMBloqYjk8Zy8@nbwork.lan \
--to=a.filippov@yadro.com \
--cc=fercerpav@gmail.com \
--cc=openbmc@lists.ozlabs.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).