You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Today Packer supports specifying certificate-based bearer JWT assertion through client_jwt parameter, or automatically getting it from the IMDS endpoint available for IaaS VMs. But in scenarios like App Service Web Jobs, neither of these are an option.
Today Packer supports specifying certificate-based bearer JWT assertion through client_jwt parameter, or automatically getting it from the IMDS endpoint available for IaaS VMs. But in scenarios like App Service Web Jobs, neither of these are an option.
In App Service for instance, there is a REST endpoint to get the token which is different from the IMDS endpoint.
https://docs.microsoft.com/en-us/azure/app-service/overview-managed-identity#using-the-rest-protocol
Ability to either specify the exact access token to use, or to use the REST protocol specified above would help to run Packer in these environments.
The text was updated successfully, but these errors were encountered: