df3956fafe
Now it logs the failure on debug and on trace it also logs the full stack trace. There's no point in logging it on info as a lot of the failures that will be logged are just fine (e.g. esusers will fail to authenticate and log the failure, but LDAP will succeed). This logging should only be applied for debugging purposes... for normal logging we have the audit logs While at it, also cleaned up the Ldap realm code... change java.lang.SecurityException to shield's LdapException Closes elastic/elasticsearch#281 Original commit: elastic/x-pack-elasticsearch@d5f0ad2efb |
||
|---|---|---|
| .esvm-shield-config | ||
| dev-tools | ||
| src | ||
| .esvmrc | ||
| LICENSE.txt | ||
| README.asciidoc | ||
| all-signatures.txt | ||
| core-signatures.txt | ||
| pom.xml | ||
| test-signatures.txt | ||
| tests.policy | ||
README.asciidoc
= Elasticsearch Security Plugin This plugins adds security features to elasticsearch You can build the plugin with `mvn package`. The documentation is put in the `docs/` directory.