Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature Request] Region auto enable on env variable #862

Open
bgavrilMS opened this issue Sep 20, 2024 · 0 comments
Open

[Feature Request] Region auto enable on env variable #862

bgavrilMS opened this issue Sep 20, 2024 · 0 comments
Labels
confidential-client For issues related to confidential client apps Feature Request Request for new functionality

Comments

@bgavrilMS
Copy link
Member

Region auto-enable

  1. On creation of a ConfidentialClientApplication, MSAL shall detect env variable MSAL_FORCE_REGION, which will be set to a specific region (e.g. westus1)
  2. If this env variable is set, MSAL shall opt-in to ESTS-R with the value of this variable.

Disabling the behavior

If region is explicitly set in MSAL to the string "DisableMsalForceRegion`, then the above no longer applies

Conflicts with WithAzureRegion(xyz)

Use of the api WithRegion(xyz) takes precedence over the env variable.

Acceptance tests

For all of the tests, assume env variable MSAL_FORCE_REGION=eastus

  1. No other config is used. ACTUAL region used: eastus
  2. App developer configures region "westus" in MSAL. ACTUAL region used: westus
  3. App developer configures region "DisableMsalForceRegion" in MSAL. ACTUAL region used: none

Original issue:

AzureAD/microsoft-authentication-library-for-dotnet#4930

@bgavrilMS bgavrilMS added Feature Request Request for new functionality confidential-client For issues related to confidential client apps labels Sep 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
confidential-client For issues related to confidential client apps Feature Request Request for new functionality
Projects
None yet
Development

No branches or pull requests

1 participant