Issue with Azure KeyVault Secret Naming for Umbraco UIBuilder License

[erikjanwestendorp]

Issue
At the moment, it is somewhat difficult to use an Azure KeyVault for configuring the Umbraco UIBuilder license.

The name of a secret may only contain alphanumeric characters and dashes. When using the Azure.Extensions.AspNetCore.Configuration.Secrets package, double dashes are automatically replaced by a colon. However, the issue lies in the dot in Umbraco.UIBuilder. A dot is not allowed in a KeyVault secret name.

Would it be possible to rename this setting to UmbracoUIBuilder, without the dot?

"Umbraco": {
    "Licenses": {
        "Products": {
            "UIBuilder": "YOUR_LICENSE_KEY"
        }
    }
}

Perhaps "Umbraco" is redundant anyway since we are already in the Umbraco section?

Steps To Reproduce
Configure an Azure KeyVault:
https://docs.umbraco.com/umbraco-cms/extending/key-vault
Try to add the license key to the KeyVault

[acoumb]

Hi @erikjanwestendorp ,

Have you tried using _ instead of .? Our licensing service supports that.

"Umbraco_UIBuilder": "YOUR_LICENSE_KEY"

[erikjanwestendorp]

Hi @acoumb, thanks for your reply! 😄 Unfortunately a _ is also not a valid character in an Azure Key Vault. Of course, we can implement a custom KeyVaultSecretManager ourselves as a workaround (see also: Handling Azure Key Vault Secret Naming with Umbraco UIBuilder License Configuration) but this is not ideal since it deviates from the default behavior.

Is it possible to change the name of the key to just UIBuilder instead of Umbraco.UIBuilder ? Since we're already in the Umbraco section, it might be a bit redundant. I'm aware that this might be a breaking change, but perhaps a fallback or something similar could be used?