Polishing.
Reformat code. Simplify flow. See gh-689 Original pull request: gh-802
This commit is contained in:
@@ -743,6 +743,41 @@ See also:
|
||||
* https://www.vaultproject.io/docs/secrets/cubbyhole/index.html[Vault Documentation: Cubbyhole Secret Backend]
|
||||
* https://www.vaultproject.io/docs/concepts/response-wrapping.html[Vault Documentation: Response Wrapping]
|
||||
|
||||
[[vault.authentication.jwt]]
|
||||
== JWT authentication
|
||||
|
||||
Configuring JWT authentication requires the token or a JWT supplier.
|
||||
You can configure the authentication via `JwtAuthenticationOptions`.
|
||||
|
||||
On the Vault side you can configure the JWT backend by enabling the JWT auth backend and creating a role.
|
||||
You can either use `oidc_discovery_url`, `jwks_url` or `jwt_validation_pubkeys` to configure the JWT backend.
|
||||
|
||||
====
|
||||
[source,java]
|
||||
----
|
||||
@Configuration
|
||||
class AppConfig extends AbstractVaultConfiguration {
|
||||
|
||||
// …
|
||||
|
||||
@Override
|
||||
public ClientAuthentication clientAuthentication() {
|
||||
|
||||
JwtAuthenticationOptions options = JwtAuthenticationOptions.builder()
|
||||
.role(…).jwt(…).path(…).build();
|
||||
|
||||
return new JwtAuthentication(options, restOperations());
|
||||
}
|
||||
|
||||
// …
|
||||
}
|
||||
----
|
||||
====
|
||||
|
||||
See also:
|
||||
|
||||
* https://developer.hashicorp.com/vault/docs/auth/jwt[Vault Documentation: Using the JWT auth backend]
|
||||
|
||||
[[vault.authentication.kubernetes]]
|
||||
== Kubernetes authentication
|
||||
|
||||
@@ -828,42 +863,6 @@ See also:
|
||||
* https://www.vaultproject.io/api-docs/auth/radius[Vault Documentation: Using the RADIUS auth backend]
|
||||
* https://www.vaultproject.io/api-docs/auth/okta[Vault Documentation: Using the Okta auth backend]
|
||||
|
||||
[[vault.authentication.jwt]]
|
||||
== JWT authentication
|
||||
|
||||
|
||||
Configuring JWT authentication requires at least the signed JWT to be provided:
|
||||
|
||||
====
|
||||
[source,java]
|
||||
----
|
||||
@Configuration
|
||||
class AppConfig extends AbstractVaultConfiguration {
|
||||
|
||||
// …
|
||||
|
||||
@Override
|
||||
public ClientAuthentication clientAuthentication() {
|
||||
|
||||
JwtAuthenticationOptions options = JwtAuthenticationOptions.builder()
|
||||
.role(…).jwt(…).path(…).build();
|
||||
|
||||
return new JwtAuthentication(options, restOperations());
|
||||
}
|
||||
|
||||
// …
|
||||
}
|
||||
----
|
||||
====
|
||||
You can configure the authentication via `JwtAuthenticationOptions`.
|
||||
|
||||
On the Vault side you can configure the JWT backend by enabling the JWT auth backend and creating a role. You can either use `oidc_discovery_url`, `jwks_url` or `jwt_validation_pubkeys` to configure the JWT backend.
|
||||
|
||||
See also:
|
||||
|
||||
* https://developer.hashicorp.com/vault/docs/auth/jwt[Vault Documentation: Using the JWT auth backend]
|
||||
|
||||
|
||||
[[vault.authentication.steps]]
|
||||
== Authentication Steps
|
||||
|
||||
|
||||
Reference in New Issue
Block a user