Similar to #49, including the response body in the exception thrown for auth failures provides information that is helpful for debugging failed logins.
Add the response body to the VaultException thrown when an Auth method fails.
I've also fixed up a couple of issues that the build complained about:
> Task :javadoc
...
/Users/mgrass/src/vault-java-driver/src/main/java/com/bettercloud/vault/VaultConfig.java:216: error: @param name not found
* @param prefixPathDepth integer number of path elements in the prefix path
^
...
> Task :javadoc FAILED
Similar to #49, including the response body in the exception thrown for auth failures provides information that is helpful for debugging failed logins.
Add the response body to the VaultException thrown when an Auth method fails.
I've also fixed up a couple of issues that the build complained about:
Unfortunately, it looks like compilation of tests was broken by https://github.com/BetterCloud/vault-java-driver/pull/189; based on https://github.com/BetterCloud/vault-java-driver/pull/189#issuecomment-546507585 it sounds like @steve-perkins has a fix on the way for the broken tests, so I haven't touched those.