[SOLUTION] Invalid credentials | nfs-idmapd | No Special Chars in PW allowed | Inline Commenting Allowed in INI-Config-Parser

Jan  9 18:37:49 jammy-server rpc.idmapd[49195]: nfsdcb: authbuf=gss/krb5p authtype=group
Jan  9 18:37:49 jammy-server rpc.idmapd[49195]: nfs4_gid_to_name: calling umich_ldap->gid_to_name
Jan  9 18:37:49 jammy-server rpc.idmapd[49195]: ldap_init_and_bind: version mismatch between API information and protocol version. Setting protocol version to 3
Jan  9 18:37:49 jammy-server rpc.idmapd[49195]: ldap_init_and_bind: ldap_simple_bind_sto [ldap://jammy.server:389] as user 'uid=idmapd-user,ou=user,dc=jammy,dc=server': Invalid credentials (49)
Jan  9 18:37:49 jammy-server rpc.idmapd[49195]: nfs4_gid_to_name: umich_ldap->gid_to_name returned -22
Jan  9 18:37:49 jammy-server rpc.idmapd[49195]: nfs4_gid_to_name: final return value is -22
Jan  9 18:37:49 jammy-server rpc.idmapd[49195]: Server : (group) id "10000" -> name "nogroup"

[Problem]
You can not use an '#' or an ';' in your LDAP_passwd in your /etc/idmapd.conf

[WRONG]
LDAP_passwd = MY_ULTRA#;;#SECURE_PASSWORD
idmap sends to ldap: 'MY_ULTRA' <- that's your parsed password. 

[CORRECT]
LDAP_passwd = ULTRA_SECURE_PASSWORD_WITHOUT_SPECIAL_CHARACTERS

[Why]

The rpc.idmapd/nfs-idmapd.service has an INI-Config-Parser which allows inline commenting. 
So the parser strips your PW after an '#' or an ';' and interprets it as an inline comment. 

That is new in idmapd! 
A "MY#PASSWORD#IS;SECURE" becomes than "MY", that's it. 
Everything after the '#' or ';' is gone!