skastberg/integrate-2022

Examples from my presentation at Integrate 2022

integrate-2022's Issues

Issue while using the Key vault reference

Goodmorning Samuel Kastberg,

Your code and bicep file works flawlessly to create a connectionKey for the managed connections. Thanks! But i am having issues to use the Keyvault reference.

While using the Keyvault reference in my local.settings.json:

"apicon-storage-connectionKey": "@Microsoft.KeyVault(VaultName=keyvaultname;SecretName=apicon-storage-connectionKey)",

i am receiving the following error on action execution in the workflow:

{ "status": 400, "source": "", "message": "Error from token exchange: Bad Key authorization token. Token must be a valid JWT signed with HS256\r\nInvalid JWT token. IDX12741: JWT: 'System.String' must have three segments (JWS) or five segments (JWE).\r\n" }

It sounds to me like it could be 2 things:

1. it does not understand the reference and uses the referencestring as input for the connectionKey
2. The keyvault reference cannot authenticate to the Keyvault itself.

Ive checked the second option and i do have access (with my user account) to the keyvault secret, because the bicep file executed without issue underneath the same user account.

While using the connection key value directly within the local.settings.json it works.

Do you have any suggestions on how to resolve this issue, i would rather use the Keyvault reference as this would save some time "copy and pasting" connection keys