According to documentation:
"direct-verification - Does this realm support verification of credentials by directly connecting to LDAP as the account being authenticated"
We
should be able to authenticate with a valid ldap account without having
to specify the principal and credential on ldap dir-context
authentication. However this is not the case.
After
checking the source code, this happens because the getIdentity doesn't
honor the direct-verification flag and always uses the principal of the
dir context. With direct verification enabled, all connections to ldap
should use the account that is being authenticated (in my opinion). This
will benefit the security, because there is one less user/password on
the configuration file (standalone.xml).
Is this a bug or the expected setup/behaviour of the ldap realm?
Thanks