CR Vault - auth backend some parameters

[thdonatello]

Hi! I want to use two auth backends with vault: kubernetes and oidc (keycloak).
I used terraform to create oidc provider:

resource "vault_jwt_auth_backend" "keycloak" {
  path               = "keycloak"
  type               = "oidc"
  default_role       = "default"
  oidc_discovery_url = var.vault_oidc_discovery_url
  oidc_client_id     = keycloak_openid_client.openid_client.client_id
  oidc_client_secret = keycloak_openid_client.openid_client.client_secret

  tune {
    audit_non_hmac_request_keys  = []
    audit_non_hmac_response_keys = []
    default_lease_ttl            = "1h"
    listing_visibility           = "unauth"
    max_lease_ttl                = "1h"
    passthrough_request_headers  = []
    token_type                   = "default-service"
  }
}

As you can see, I have several additional properties such as listing_visibility . But I can't do this by CR vault.
Can anyone explain to me how I can do this?

[jasaltvik]

We're also trying to set listing_visibility via the Vault CR, and we're also not sure if this is supported or not? Thanks for any input on this.

[tomsozolins]

If anyone interested, it can be configured like this:

    auth:
      - type: jwt
        options:
          listing_visibility: "unauth"