François Van Der Biest

I was not sure Geonetwork respects the `Accept-Language` header but it seems he does !

Thanks for taking the time to elaborate a proposal Florent. I have to admit I'm not a big fan of having a GET lang parameter... Why not sticking to what...

Same with the proxy: proxy_1 | WARNING: An illegal reflective access operation has occurred proxy_1 | WARNING: Illegal reflective access by com.sun.xml.bind.v2.runtime.reflect.opt.Injector (file:/var/lib/jetty/webapps/ROOT/WEB-INF/lib/jaxb-impl-2.2.11.jar) to method java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int) proxy_1 | WARNING: Please...

I'm puzzled ! Please share the map context, eventually directly with me.

Gave it a try for 22.0, but not straigtforward => will require some $$$funding$$$

Discussing it with @jahow - maybe we should use the public API for this

We also have this FOSS4G 2022 quick start guide with docker: https://docs.google.com/document/d/1_SmwYqe6VExtmxcLAH86jarj9j6iXs0rq8FSsAT1LI8/edit?usp=sharing

FYI, 18.12 will bring the ability to forbid the user to modify its login, see https://github.com/georchestra/datadir/blob/18.12/console/console.properties#L29-L31 and #2162

The issue seems server-side since the `/console/private/users` webservice produces lowercased uid Eg for user `FVanderbiest`: ```js { uid: "fvanderbiest", givenName: "François", sn: "Van Der Biest", org: "Camptocamp", orgId: "C2C", mail:...

> If I correctly understand, username is always stored lowercase in LDAP. Should we prevent users from creating logins with uppercased chars then ?