1.5.0-beta.2 (2021-07-12)
New Features
- Added support to
ManagedIdentityCredential
for Bridge to Kubernetes local development authentication. - TenantId values returned from service challenge responses can now be used to request tokens from the correct tenantId. To support this feature, there is a new
AllowMultiTenantAuthentication
option onTokenCredentialOptions
.- By default,
AllowMultiTenantAuthentication
is false. When this option property is false and the tenant Id configured in the credential options differs from the tenant Id set in theTokenRequestContext
sent to a credential, anAuthorizationFailedException
will be thrown. This is potentially breaking change as it could be a different exception than what was thrown previously. This exception behavior can be overridden by either setting anAppContext
switch named "Azure.Identity.EnableLegacyTenantSelection" totrue
or by setting the environment variable "AZURE_IDENTITY_ENABLE_LEGACY_TENANT_SELECTION" to "true". Note: AppContext switches can also be configured via configuration like below:
- By default,
<ItemGroup>
<RuntimeHostConfigurationOption Include="Azure.Identity.EnableLegacyTenantSelection" Value="true" />
</ItemGroup>