You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
This is a presentation error. The config can be changed at runtime. Even if the documentation says it's fixed at build time. I don't know why this is the case.
ElytronSecurityLdapProcessor#configureLdapRealmAuthConfig has the annotation: Record(ExecutionTime.RUNTIME_INIT)
On your second point I fully aggree.
gsmet
changed the title
LDAP Security - configuration needs to be modifyable at runtime
LDAP Security - configuration needs to be modifiable at runtime
Jun 29, 2020
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
The text was updated successfully, but these errors were encountered: