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

Add configuration for reactive Vault client #133

Closed
mp911de opened this issue Jul 10, 2017 · 0 comments
Milestone

Comments

@mp911de
Copy link
Member

@mp911de mp911de commented Jul 10, 2017

No description provided.

@mp911de mp911de added this to the 2.0.0 M2 milestone Jul 10, 2017
mp911de added a commit that referenced this issue Jul 10, 2017
Closes gh-133.
@mp911de mp911de closed this Jul 10, 2017
nwarnke pushed a commit to nwarnke/spring-cloud-vault that referenced this issue Feb 27, 2019
We now support AppRole authentication pull mode by fetching roleId/secretId from Vault's AppRole auth backend using an initial (ephemeral token) if roleId/secretId are not configured.

Original pull request: spring-cloudgh-133.
Related ticket: spring-cloudgh-132.
nwarnke pushed a commit to nwarnke/spring-cloud-vault that referenced this issue Feb 27, 2019
Fetch SecretId if no secretId is configured but an initial token is provided instead of relying on a configured role name. Use configured AppRole mount path instead of static literal. Reorder methods, add since and author tags. Reduce tests to AppRoleAuthenticationOptions code. Add further test cases. Add integration tests. Formatting, fix typos.

Original pull request: spring-cloudgh-133.
Related ticket: spring-cloudgh-132.
nwarnke pushed a commit to nwarnke/spring-cloud-vault that referenced this issue Feb 27, 2019
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.