welcome to NethServer Community!
I could reproduce your problem and it seems that some binary passwords are working with sogo while others don’t. For ejabberd I had to use an AD user, the machine account was not working.
For making sogo work you may unbind/rebind your AD to get another bind password.
For ejabberd change two lines in /etc/ejabberd/ejabberd.cfg and enter previously created AD user credentials:
This is just a workaround working until next reboot or config change. If it works for you, we may create a custom template so it will be applied permanently.
This is my not working binary password killing sogo:
I isolated the char breaking sogo, it’s just this one in this case: “” <- put this char in your sogo.conf even as comment and sogo won’t start anymore… @stephdl, @mark_nl, do you have an idea how to find out which chars are killing sogo and not use them in bind password anymore?