Support '/' characters in credential IDs

[chriskilding]

What feature do you want to see added?

(This is really a question about how Azure Keyvault Plugin behaves at the moment, but depending on the answer it could become a feature request.)

The / (forward slash) character is sometimes used to namespace credentials e.g. staging/foobar or production/foobar. This is more prevalent in cloud secrets manager services, where / is used to mimic folder structures.

Does the Azure Keyvault Plugin support credentials with / in their IDs?

• If it does, how/where does it urlencode the credential ID for presentation (so that it doesn't break the Jenkins credentials Web UI)?
• If it does not, should support be added for it?

For comparison, the default (local disk) credentials provider has client side validation that tries to stop you using / in new credentials that you add - only A-Za-z0-9 and _ - . are allowed. But if you bypass this validation, in some scenarios it is able to display credential IDs with / characters just fine.

Upstream changes

No response

[timja]

It would work to use / as a namespace because Azure Key Vault credentials can't have a / in their name:
https://docs.microsoft.com/en-us/azure/key-vault/general/about-keys-secrets-certificates

If that's what your question is about anyway