Displaying 3 results from an estimated 3 matches for "resttrict".
Did you mean:
restrict
2020 Oct 13
2
Samba SSSD authentication via userPrincipalName does not work because samba claims that the username does not exist.
On 13/10/2020 15:01, Markus Jansen via samba wrote:
> Thank you very much for your hints.
>
> I got rid of SSSD and managed to get a successful kerberos
> authentication via wbinfo -K and the UPN.
>
> But accessing via SMB (using MAC OS' smbutil or Finder) still fails with
> "FAILED with error NT_STATUS_NO_SUCH_USER".
>
> As I'm using CentOS 8, I used
2020 Oct 14
0
Samba SSSD authentication via userPrincipalName does not work because samba claims that the username does not exist.
...*not your friend* if you want any
tuning of your LDAP or related behavior, and it insists on pre-caching
all of your LDAP before completing the setup of sssd. SO it starts up,
times out on the pre-caching, and *fails* with no legible log of what
the problem was and no good way to tune it except to resttrict your
LDAP access to a wafer thin sliver of the upstream setup, *which
configuration gets overwritten!!!!* with updates of anything that uses
authconfig.
This iss a condemnation of authconfig's poor management of the
sophisticated options to sssd, but unless you're running something
like an...
2020 Oct 14
2
Samba SSSD authentication via userPrincipalName does not work because samba claims that the username does not exist.
...f you want any
> tuning of your LDAP or related behavior, and it insists on pre-caching
> all of your LDAP before completing the setup of sssd. SO it starts up,
> times out on the pre-caching, and *fails* with no legible log of what
> the problem was and no good way to tune it except to resttrict your
> LDAP access to a wafer thin sliver of the upstream setup, *which
> configuration gets overwritten!!!!* with updates of anything that uses
> authconfig.
>
> This iss a condemnation of authconfig's poor management of the
> sophisticated options to sssd, but unless you'...