Description
See https://quarkus.io/guides/security-ldap#configuration-reference
All properties are fixed at build time.  But in a realistic enterprise, these will differ between dev preprod prod environments (otherwise your dev credentials would also work in prod).  There will be individual server URLs with individual bind credentials,  users and groups are probably stored in different placess o the base dn's and filters will differ, etc..
As a bonus, the bind credentials should not be required, ldap has the concept of an anonymous bind.
-> quarkus.security.ldap.dir-context.principal and quarkus.security.ldap.dir-context.password can be null