Re: Imprecise description for nslcd.conf "map"
[
Date Prev][
Date Next]
[
Thread Prev][
Thread Next]
Re: Imprecise description for nslcd.conf "map"
- From: Philip Prindeville <philipp_subx [at] redfish-solutions.com>
 
- To: Arthur de Jong <arthur [at] arthurdejong.org>
 
- Cc: nss-pam-ldapd-users [at] lists.arthurdejong.org
 
- Subject: Re: Imprecise description for nslcd.conf "map"
 
- Date: Sun, 25 Feb 2024 14:18:10 -0700
 
> On Feb 24, 2024, at 6:54 AM, Arthur de Jong <arthur@arthurdejong.org> wrote:
> 
> On Fri, 2024-02-23 at 10:42 -0700, Philip Prindeville wrote:
>> map passwd lhs rhs
>> 
>> is the equivalent of:
>> 
>> map passwd lhs "${rhs}"
> 
> Correct. The only limitation is that for some mapped attributes this
> syntax is not allowed because the attribute names are used to build
> LDAP queries.
> 
>> which is not implied by the man page.  The manual suggests that
>> anything NOT quoted is treated as a literal string with no
>> expansions/replacements happening.
> 
> Do you have a suggestion for a clarification? This may be a bit brief
> currently:
> 
>    The NEWATTRIBUTE may be any attribute as it is available in
>    the directory.
> 
> Thanks,
I would document 2 different forms separately:
map ATTRIBUTE NEWATTRIBUTE
and:
map ATTRIBUTE "EXPRESSION"
And enumerate the exceptions.  Like uidNumber as ATTRIBUTE can't have an 
EXPRESSION expansion.