Custom auth backend name

[Gazi Dizdaroğlu]

Hello,

Is it possible to give a custom auth name instead of "jwt" on the pipe? 

https://bitbucket.org/atlassian/vault-secrets/src/master/

[Igor Stoyanov · Accepted solution]

Hi @Gazi Dizdaroğlu . New pipe version released with feature you requested:

oidc: true
script:
  - pipe: atlassian/vault-secrets:0.5.0
    variables:
      VAULT_ADDRESS: "<your vault address>"
      VAULT_OIDC_ROLE: "<your created role name with attached policies in vault>"
      VAULT_AUTH_PATH: "my-custom-jwt-path"
      SECRET_PATH: "secret/foo"

Regards, Igor

[Gazi Dizdaroğlu]

Thank you so much <3 

[Igor Stoyanov]

Hi @Gazi Dizdaroğlu . Please, provide more details to your question.

`vault auth enable jwt` is not a custom name, it is how you enable jwt.

I can not find any other occurences.

Also this example does not use jwt at all:

script:
  - pipe: atlassian/vault-secrets:0.3.0
    variables:
      VAULT_ADDRESS: "<your vault address>"
      VAULT_NAMESPACE: "<your vault namespace>"
      VAULT_TOKEN: "<your vault token>"
      SECRET_PATH: "secret/foo"

Regards, Igor

[Igor Stoyanov]

Okay, now i understood what your want according to:

plugin method is mounted at the /auth/jwt path in Vault. Since it is possible to enable auth methods at any location, please update your API calls accordingly.

Currently, pipe does not support different path, but i will add this as a feature request, and notify you when this feature will become available.

Regards, Igor