John Behm

I will add a flag

My question targets the usage of the security provider (of this module) for bearer tokens. Do you create a security provider for every new jwt? as the constructor of the...

I like this :) I also do work extensively with the generated client. Could you update the README.md in this pull request Edit: `server returned an unexpected response`

wildcard routes are not part of the official open api specification. some Java libraries allow that, but that's basically not standardized behavior.

for caddy use the proxy parameter "transparent" to fix this issue. ``` openkb.example.de { proxy / localhost:4444 { transparent } } ```

project seems dead, I found an alternative that's called bookstack.

meh: https://github.com/hvac/hvac/issues/648 I sadly don't see any support for that in the project files: https://github.com/hvac/hvac/tree/develop/hvac/api/secrets_engines

this issue is an extension of that issue: #336

@alexdepalex I think I was able to create a workaround w/o touching the module code: https://github.com/jxsl13/vault-test/blob/master/stages/07-configure-jwt.yaml Already forgot most of what I did there.

workaround: ```yaml - name: create {{ item }} jwt role hashivault_oidc_auth_role: name: "{{ item }}" mount_point: jwt # actual payload values below user_claim: sub bound_audiences: - "{{ keycloak.client_id }}" token_policies:...