OS: Red Hat Enterprise Linux 8
Browser: Firefox 78.3.0
when creating an LDAP group mapping, LDAP group names with slashes are not accepted ("… is no valid DN"). Not sure about the LDAP standard, to be honest, but my company uses slashes in their DNs.
When I manually insert the mapping directly into the “setting” DB table, everything works as expected. So it seems that the restriction is only applied by the UI without technical necessity.
Can this behavior be changed in the future?
It looks like it’s definitely not recommended using slashes:
And the recommendation is to use hex representation instead - so
/ would be
thanks for your info. Sadly I will have to live with what my employer decided to implement.
In any case, since it actually is working if I manually put the slash into the DB entry, I do not see a reason why Metabase should unnecessarily enforce good LDAP practices here.
Or can there be other cases where this might break something?
Metabase is using another library for validation:
So it would either require that the upstream function accepts slashes (perhaps newer versions does, but I haven’t tested) or we would have to write our own validator.
But if the hex representation works (you didn’t note if you had tested that), then that would be the correct way to write it.