Skip to content

Commit ec08d59

Browse files
Merge branch 'create_vault_bugfix_ab#78506' of https://github.com/Keyfactor/azurekeyvault-orchestrator into create_vault_bugfix_ab#78506
2 parents 40dd646 + 32765c0 commit ec08d59

File tree

1 file changed

+8
-3
lines changed

1 file changed

+8
-3
lines changed

README.md

Lines changed: 8 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -70,7 +70,7 @@ The high level steps required to configure the Azure Keyvault Orchestrator exten
7070

7171
1) [Configure the Azure Keyvault for client access](#configure-the-azure-keyvault-for-client-access)
7272

73-
1) [Create the Store Type in Keyfactor](#create-the-akv-certificate-store-type)
73+
1) [Create the Store Type in Keyfactor](#akv-certificate-store-type)
7474

7575
1) [Install the Extension on the Orchestrator](#installation)
7676

@@ -544,7 +544,7 @@ To use the Azure Key Vault Universal Orchestrator extension, you **must** create
544544

545545

546546
The Azure Keyvault Certificate Store Type is designed to integrate with Microsoft Azure Key Vault, enabling users to
547-
manage and automate the lifecycle of cryptographic certificates stored in Azure Key Vault through Keyfactor Command.
547+
manage and automate the lifecycle of cryptographic certificates stored in Azure Keyvault through Keyfactor Command.
548548
This Certificate Store Type represents the connection and configuration necessary to interact with specific instances of
549549
Azure Key Vault, allowing for operations such as inventory, addition, removal, and discovery of certificates and
550550
certificate stores.
@@ -565,6 +565,11 @@ However, ensuring that the orchestrator has network access to Azure endpoints is
565565
mindful of these caveats and limitations will help ensure successful deployment and use of the Azure Keyvault
566566
Certificate Store Type within your organization’s security framework.
567567

568+
> :warning:
569+
> The alias you provide when enrolling a certificate will be used as the certificate name in Azure Keyvault.
570+
> Consequently; [it must _only_ contain alphanumeric characters and hyphens](https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/resource-name-rules#microsoftkeyvault).
571+
> If you encounter the error "The request URI contains an invalid name" when attempting to perform an enrollment, it is likely due to the use of disallowed characters in the alias.
572+
568573

569574

570575

@@ -633,7 +638,7 @@ the Keyfactor Command Portal
633638
##### Advanced Tab
634639
| Attribute | Value | Description |
635640
| --------- | ----- | ----- |
636-
| Supports Custom Alias | Optional | Determines if an individual entry within a store can have a custom Alias. |
641+
| Supports Custom Alias | Required | Determines if an individual entry within a store can have a custom Alias. |
637642
| Private Key Handling | Optional | This determines if Keyfactor can send the private key associated with a certificate to the store. Required because IIS certificates without private keys would be invalid. |
638643
| PFX Password Style | Default | 'Default' - PFX password is randomly generated, 'Custom' - PFX password may be specified when the enrollment job is created (Requires the Allow Custom Password application setting to be enabled.) |
639644

0 commit comments

Comments
 (0)