Repository navigation
Release v22.131.0
The HTTP connection resolver can now authenticate to its endpoint with a bearer token, either through OAuth 2.0 client credentials or through Microsoft Entra ID with an Azure credential such as a managed identity.
Added
- Bearer-token authentication for
HttpConnectionResolver: configureClientCredentialswith a token endpoint, client id, client secret and optional scope, and the resolver caches the token until shortly before it expires, refreshes it once when the endpoint answers 401, and never logs it (#3453) Cratis.Arc.Connections.Azurepackage that authenticates the resolver with Microsoft Entra ID through an Azure credential, such as a managed identity or workload identity, using theAzureCredentialauthentication type (#3453)- An extension point,
IConnectionResolverAccessTokenProvider, for supplying resolver tokens from your own identity system (#3453)