Open tgurr opened 3 years ago
To answer myself, removing activeDirectory: true
appears to fix the problem.
Hi, sorry never saw this. I did the patch back then but still don't have Synapse in use...
I'm not very familiar with the code/all the specifications.
The error seems to happen in the search function here:
https://github.com/ma1uta/ma1sd/blob/ae5864cd91f7db57c3a99b7847c3c327980e74e8/src/main/java/io/kamax/mxisd/backend/ldap/LdapDirectoryProvider.java#L76-L84
I think the exception is thrown in line 79 where something is broken when activeDirectory: true
(in that case the a UPN
object is used to get the localpart and this expects a @
in the UID -> not present -> throws the IllegalArgumentException
).
But in that case there should be line 76 present in the logs so I cannot really follow :sweat_smile:
Could you maybe try to search login@domain
and see if it also happens then?
I can confirm that the issue is still present (ma1sd version 2.5.0). Setting activeDirectory
to false
still seems to mitigate the issue.
https://github.com/ma1uta/ma1sd/pull/71 is expected to fix this problem, however I'm still running into an issue. As can be seen in the logs the users are actually found but no result is given to Element due to the error message
Bind was found but type uid is not supported
.In the logs when doing a search via Element I have:
My ma1sd configuration has:
If it's a configuration issue on my side it would be nice if someone could tell me what needs to be changed.