Displaying 3 results from an estimated 3 matches for "ldab_access_filt".
Did you mean:
ldab_access_filter
2015 May 12
2
ldap host attribute is ignored
...dap_access_order has value host
> (Tue May 12 13:16:20 2015) [sssd[be[default]]] [be_process_init]
> (0x2000): ACCESS backend target successfully loaded from provider [ldap].
<snip>
I really don't know this level, but from the above, my first reaction is
to see if there has to be an ldab_access_filter that then leads to the
ldap_access_order in the chain.
mark
2015 May 12
0
ldap host attribute is ignored
...lue host
>> (Tue May 12 13:16:20 2015) [sssd[be[default]]] [be_process_init]
>> (0x2000): ACCESS backend target successfully loaded from provider [ldap].
> <snip>
> I really don't know this level, but from the above, my first reaction is
> to see if there has to be an ldab_access_filter that then leads to the
> ldap_access_order in the chain.
>
> mark
>
> _______________________________________________
> CentOS mailing list
> CentOS at centos.org
> http://lists.centos.org/mailman/listinfo/centos
>
>
2015 May 12
3
ldap host attribute is ignored
On 05/12/2015 06:25 AM, Ulrich Hiller wrote:
>
> i have set logging in sssd to 9:
7 might be good enough for what you want to find. I added this to
domain/default section:
access_provider = ldap
ldap_access_order = host
ldap_user_authorized_host = host
debug_level = 7
/var/log/sssd/sssd_default.log logged the following for one user which
had no "host" attribute, and was