** Tags removed: bitesize
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1188475
Title:
ldap group doesn't work
To manage notifications about this bug go to:
https://bugs.launchpad.net/cyr
Hi @sles,
I marked this bug as invalid because there was no answer to my question
in comment #6 for close to two months, and launchpad wouldn't set this
bug to expired. Also when I checked, upstream hadn't commented on your
github issue.
I still don't understand fully why the original behaviour i
For some reason bug expiration isn't working for this bug. Given that
there were no updates for over two months, I'm marking it as invalid.
Feel free to reopen it if you have more information about the problem.
Thanks!
** Changed in: cyrus-sasl2 (Ubuntu)
Status: Incomplete => Invalid
--
Can you share your saslauthd configuration, and portions of your DIT
showing how the users and groups are organised?
At first glance, it feels correct to be using the user's DN to check for
group membership. I would certainly expect to be able to tell which
groups I belong to without having to res
User filed upstream bug at https://github.com/cyrusimap/cyrus-
sasl/issues/427
** Bug watch added: github.com/cyrusimap/cyrus-sasl/issues #427
https://github.com/cyrusimap/cyrus-sasl/issues/427
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subs
btw, more correct patch, which revert back bind from config in
lak_auth_bind
diff -ur lak.c.orig lak.c
--- lak.c.orig2013-06-07 09:15:20.098788278 +0400
+++ lak.c2013-06-08 10:17:07.548233104 +0400
@@ -1448,8 +1448,25 @@
if ( rc == LAK_OK &&
(ISSET(lak->conf->group_dn) ||
** Changed in: cyrus-sasl2 (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cyrus-sasl2 in Ubuntu.
https://bugs.launchpad.net/bugs/1188475
Title:
ldap group doesn't work
To manage notificat
