On (05/05/15 15:04), Jean-Baptiste Denis wrote:
I executed attached script as a root.
Thank your for sharing the script.
I reproduce the bug with it after some iterations :
# ./reproduce.sh
Stopping sssd: [ OK ]
Starting sssd:
Hi!
I can't get dyndns_update to work when I have ldap as id_provider.
Having set debug_level = 9, I do not see any update add/delete entries in
my sssd logfile.
Setting ad as id_provider solves this. Is this by design, or just the way
it is supposed to work?
Regards,
Torgeir
On (05/05/15 14:36), Jean-Baptiste Denis wrote:
...
We're using rfc2307 schema and default ldap_group_object_class value
(posixGroup). Besides that, I don't see what could explain that you can't
reproduce the problem. Chris Petty is using AD hence rc2307bis schema. So I
don't know if it is
On Tue, May 05, 2015 at 01:35:20PM +0200, Lukas Slebodnik wrote:
On (05/05/15 12:16), Simon wrote:
Hi,
I have configured an Ubuntu 14.04 server to authenticate against, and use
attributes from, Active Directory running on Server 2008 R2.
However, I have a seemingly odd issue whereby user
On (05/05/15 12:16), Simon wrote:
Hi,
I have configured an Ubuntu 14.04 server to authenticate against, and use
attributes from, Active Directory running on Server 2008 R2.
However, I have a seemingly odd issue whereby user environment variables
(which are initially set correctly) get lost on
On Tue, May 05, 2015 at 02:59:18PM +0200, Lukas Slebodnik wrote:
On (05/05/15 12:29), torgeir.wulfsb...@kongsberg.com wrote:
Hi!
I can't get dyndns_update to work when I have ldap as id_provider.
Having set debug_level = 9, I do not see any update add/delete entries
in my sssd logfile.
On (30/04/15 14:29), Chris Petty wrote:
Here is my domain section … reproducible every time if i clear the sssd cache.
[domain/default]
debug_level = 9
id_provider = ad
auth_provider = ad
access_provider = ldap
chpass_provider = ad
ad_domain = dhe.duke.edu
ldap_search_base =
Hi,
I think this problem may be part (or related to) the FreeIPA/SSSD
LDAP cross-forest trust slow queries issue, but I'm not sure.
We've been testing sssd on our RHEL6 and RHEL7 hosts, using the latest
available packages. We have a fairly simple sssd configuration. We
use the ad provider with
On (05/05/15 15:41), Jean-Baptiste Denis wrote:
I added sleep 9 later, because I was not able to reproduce your bug.
The results can be influenced byt the fact I used fedora for testing and sssd
master.
OK. I've tested with 1.12.4, but not with the master since I don't have python3
available
http://linux.die.net/man/3/fnmatch
Ah yes, I see : sounds to be the right function indeed. To be honnest
I'm not volunteering, but I promise will look at it.
Netgroups are not supported in ldap_user_authorized_host either.
So it will not work.
if pam_access support it (I think it does) it
python3 was optional from beginning but we recently added hint to configure
script how to disable it.
sssd-1.12 is very close to master so I do not expect any difference.
Indeed.
I've just compiled the git master (56552c518a07b45b25d4a2ef58d37fac0918ce60) and
was still able to reproduce the
On (05/05/15 18:10), Olivier wrote:
Thank you Lukas,
My question is : are jokers supported in the host attribute ?
Answer is no.
Although it shoudl not be difficult to implemennt it.
I would suggest to look into function sdap_access_host
in src/providers/ldap/sdap_access.c and function
Hi,
I have configured an Ubuntu 14.04 server to authenticate against, and
use attributes from, Active Directory running on Server 2008 R2.
However, I have a seemingly odd issue whereby user environment variables
(which are initially set correctly) get lost on the second (or third)
and then
13 matches
Mail list logo