Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upgrade to Spring Vault 2.0.1 #203

Closed
mp911de opened this issue Apr 5, 2018 · 0 comments

Comments

@mp911de
Copy link
Member

@mp911de mp911de commented Apr 5, 2018

No description provided.

@mp911de mp911de added this to the 2.0.0 RC1 milestone Apr 5, 2018
@mp911de mp911de closed this in fec3564 Apr 5, 2018
nwarnke pushed a commit to nwarnke/spring-cloud-vault that referenced this issue Feb 27, 2019
We now throw a more specific exception (VaultLoginException) in cases login fails. Exception creation considers HTTP and other causes extracting relevant details and pulls this into a single method rather than spreading message construction in various places.

See spring-cloudgh-203.
nwarnke pushed a commit to nwarnke/spring-cloud-vault that referenced this issue Feb 27, 2019
Catch RuntimeException in LifecycleAwareSessionManager on revocation.

See spring-cloudgh-203.
nwarnke pushed a commit to nwarnke/spring-cloud-vault that referenced this issue Feb 27, 2019
We now log the HTTP status text along the HTTP status itself and a potential error message. Client errors (HTTP status 4xx) are logged on WARN level as feedback to the application as client errors aren't considered fatal.

We also introduce VaultSessionManagerException and VaultTokenRenewalException to provide exceptions with a specific context.

Closes spring-cloudgh-257.
Related ticket: spring-cloudgh-203.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
1 participant
You can’t perform that action at this time.