Conversation
…t sync Add optional contentType field to GetAzureKeyVaultSecret interface and create AzureKeyVaultSyncOptionsSchema with disableCertificateImport field. Update the base schema builders to accept sync options schemas as a parameter, allowing destination-specific options to be included in create/update sync endpoints.
… Vault sync Add certificate content type detection to filter out application/x-pkcs12 and application/x-pem-file secrets when disableCertificateImport option is enabled. Filtering happens at the list stage before fetching individual secret values, avoiding unnecessary API calls. Update all three sync operation handlers (create, update, delete) to pass the option to the fetch function.
Add description for the new AZURE_KEY_VAULT.disableCertificateImport option in the SecretSyncs constants, making it available for API documentation.
Update TAzureKeyVaultSync type to include disableCertificateImport as an optional field in syncOptions, matching the backend schema.
Add disableCertificateImport field to AzureKeyVaultSyncDestinationSchema as an optional boolean that defaults to false.
Create AzureKeyVaultSyncOptionsFields component with a toggle switch for the disableCertificateImport option, including tooltip documentation. Wire it into SecretSyncOptionsFields switch statement to render for Azure Key Vault syncs.
Update oauthSchema to make tenantId optional since OAuth flow doesn't require it for Azure Key Vault connections. Fix submit button disable logic to properly allow submission for new OAuth connections.
Add documentation for the new Disable Certificate Import option in the Azure Key Vault sync configuration guide, explaining when and why to enable it. Update the vault-options.png screenshot to show the new option.
Collaborator
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
Contributor
Author
|
@greptile review this! |
Contributor
Greptile SummaryThis PR adds a Key changes:
Two issues worth attention:
Confidence Score: 3/5
Important Files Changed
Last reviewed commit: "refactor(secret-sync..." |
backend/src/services/secret-sync/azure-key-vault/azure-key-vault-sync-fns.ts
Outdated
Show resolved
Hide resolved
varonix0
requested changes
Mar 19, 2026
backend/src/services/secret-sync/azure-key-vault/azure-key-vault-sync-fns.ts
Outdated
Show resolved
Hide resolved
backend/src/services/secret-sync/azure-key-vault/azure-key-vault-sync-types.ts
Outdated
Show resolved
Hide resolved
...pConnections/AppConnectionsPage/components/AppConnectionForm/AzureKeyVaultConnectionForm.tsx
Outdated
Show resolved
Hide resolved
varonix0
approved these changes
Mar 22, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Context
This PR implements a new "Disable Certificate Import" option for Azure Key Vault Secret Sync. When enabled, Infisical will skip importing certificate-backed secrets (those with contentType
application/x-pkcs12orapplication/x-pem-file) from Azure Key Vault.Why: Azure Key Vault exposes certificates through the Secrets API, which some users want to filter out to keep their Infisical secrets project focused only on actual secrets rather than certificate objects.
How it works: The filtering happens at the list stage (before fetching individual secret values) using the
contentTypefield returned in the AKV List Secrets API response, avoiding unnecessary API calls.Related ticket: ENG-4687
Changes
Backend
contentType?: stringfield toGetAzureKeyVaultSecretinterface to capture certificate type informationAzureKeyVaultSyncOptionsSchemawithdisableCertificateImportboolean optionFrontend
TAzureKeyVaultSynctype to includedisableCertificateImportin syncOptionsdisableCertificateImportfield toAzureKeyVaultSyncDestinationSchema(optional, defaults to false)AzureKeyVaultSyncOptionsFieldscomponent with a toggle switch and tooltipSecretSyncOptionsFieldsswitch statementDocumentation
Steps to verify the change
Screenshots
Updated vault-options.png showing the new toggle in the UI configuration screen.
Type
Checklist