Getting AccessToKeyVaultDenied error in azure portal for function app, even though managed identity has roles KeyVaultReader and KeyVaultSecretsUser
I have set up a Function app in azure. I have created a key vault in the same region. I set the function app to use system managed identity. I granted the KeyVaultReader and KeyVaultSecretsUser roles to the function app’s managed identity. (The Key vault is configured to use RBAC). When I define an application setting which should be able to use a Key Vault Reference, my supposition is that I should see an absence of errors in the listing on the Azure portal.
The operation is not allowed by RBAC
In AzureKeyVault Access Control (IAM)
When I click View my access
I see I have the owner role with inherited scope, condition None.
Azure KeyVault Certificate with non-exportable key can still export the key through KeyVault Secret
For digital signature of files, I have a PKCS12 in hand with all necessary key material (e.g. private key + signature certificate + certificate chain).
Does length of key have an any impact on performance in Azure Keyvalut?
Does having a long key in Azure Keyvault affect in any way the performance taking into consideration that data might be added to Keyvault in very large volumes? (hundreds of entries daily)
if key is too long in azure keyvalut, does it have any impact on performance?
If key is too long in azure keyvalut, does it have any impact on performance considering that data might be added to keyvault in 100’s every day.