search for: be_process_init

...> (Tue May 12 13:16:20 2015) [sssd[be[default]]] [dp_get_options] > (0x0400): Option ldap_access_filter has no value > (Tue May 12 13:16:20 2015) [sssd[be[default]]] [dp_get_options] > (0x0400): Option ldap_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

...switch to "ldap_id_mapping = true". After this sssd refuses to start. The logfile says: (Wed Aug 27 10:18:11 2014) [sssd[be[invis-ad.loc]]] [load_backend_module] (0x0010): Error (5) in module (ad) initialization (sssm_ad_id_init)! (Wed Aug 27 10:18:11 2014) [sssd[be[invis-ad.loc]]] [be_process_init] (0x0010): fatal error initializing data providers (Wed Aug 27 10:18:11 2014) [sssd[be[invis-ad.loc]]] [main] (0x0010): Could not initialize backend [5] Our smb.conf: -------------------------------------------------------- [global] workgroup = INVIS-AD realm = invis-ad.loc...

...[be[ronnyforberger.de]]] [ad_set_ad_id_options] (0x0040): Cannot set the SASL-related options (Fri Nov 11 17:10:11 2016) [sssd[be[ronnyforberger.de]]] [load_backend_module] (0x0010): Error (2) in module (ad) initialization (sssm_ad_id_init)! (Fri Nov 11 17:10:11 2016) [sssd[be[ronnyforberger.de]]] [be_process_init] (0x0010): fatal error initializing data providers (Fri Nov 11 17:10:11 2016) [sssd[be[ronnyforberger.de]]] [main] (0x0010): Could not initialize backend [2] I thought this is because of not having joined the domain. It's complaining about the keytab. Do you have any ideas here? Best regards,...

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

...13:16:20 2015) [sssd[be[default]]] [dp_get_options] >> (0x0400): Option ldap_access_filter has no value >> (Tue May 12 13:16:20 2015) [sssd[be[default]]] [dp_get_options] >> (0x0400): Option ldap_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. &g...

...e. Therefore i do have: (Tue May 12 13:16:20 2015) [sssd[be[default]]] [dp_get_options] (0x0400): Option ldap_access_filter has no value (Tue May 12 13:16:20 2015) [sssd[be[default]]] [dp_get_options] (0x0400): Option ldap_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]. "Requesting attrs: [objectClass]" and "Requesting attrs: [host]" are in the logfile. So there is no access check apart from username and password check - otherwise i would not have been able to login....

Hi, I want to authenticate against Samba 4 using samba and sssd on FreeBSD using this guide: http://serverfault.com/questions/599200/how-to-integrate-active-directory-with-freebsd-10-0-using-security-sssd The problem is, the machine I want to install authentication on is the domain controller itsself. So the following commands show the errors: net ads join