Having an Avatar Picture Field Mapping value configured in LDAP settings breaks LDAP authentication.
Expected behavior
Having an Avatar Picture Field Mapping configured in LDAP settings should not break LDAP authentication.
Steps to reproduce the behavior
Configure the LDAP authentication in strategy with appropriate values. In our case the Avatar Picture Field Mapping value should be "thumbnailPhoto". Create a new user using the LDAP strategy. Attempt to login as that user and we get the error as shown in the screenshot. Removing the value in Avatar Picture Field Mapping works around the error and allows the user to log in.
I'm pretty sure we store the image file directly in thumbnailPhoto attribute... I'm not sure if that might be the issue here if some other value is expected.
Version: Wiki.js 2.0.0-beta.275 using Docker
Actual behavior
Having an Avatar Picture Field Mapping value configured in LDAP settings breaks LDAP authentication.
Expected behavior
Having an Avatar Picture Field Mapping configured in LDAP settings should not break LDAP authentication.
Steps to reproduce the behavior
Configure the LDAP authentication in strategy with appropriate values. In our case the Avatar Picture Field Mapping value should be "thumbnailPhoto". Create a new user using the LDAP strategy. Attempt to login as that user and we get the error as shown in the screenshot. Removing the value in Avatar Picture Field Mapping works around the error and allows the user to log in.
I'm pretty sure we store the image file directly in thumbnailPhoto attribute... I'm not sure if that might be the issue here if some other value is expected.