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
@@ -253,11 +264,11 @@ public T authority(String val) throws MalformedURLException {
253
264
254
265
/**
255
266
* Set URL of the authenticating B2C authority from which MSAL will acquire tokens
256
-
*
267
+
* <p>
257
268
* Valid B2C authorities should look like: https://<something.b2clogin.com/<tenant>/<policy>
258
-
*
269
+
* <p>
259
270
* MSAL Java also supports a legacy B2C authority format, which looks like: https://<host>/tfp/<tenant>/<policy>
260
-
*
271
+
* <p>
261
272
* However, MSAL Java will eventually stop supporting the legacy format. See here for information on how to migrate to the new format: https://aka.ms/msal4j-b2c
262
273
*
263
274
* @param val a boolean value for validateAuthority
@@ -393,10 +404,10 @@ public T clientCapabilities(Set<String> capabilities) {
393
404
* Indicates that the library should attempt to discover the Azure region the application is running in when
394
405
* fetching the instance discovery metadata. Regions can only be detected when running in an Azure environment,
395
406
* such as an Azure VM or other service, or if the environment has environment variable named REGION_NAME configured.
396
-
*
407
+
* <p>
397
408
* Although you can enable both autodetection here and a specific region with {@link AbstractClientApplicationBase#azureRegion} at the same time,
398
409
* the region set with {@link AbstractClientApplicationBase#azureRegion} will take priority if there is a mismatch.
399
-
*
410
+
* <p>
400
411
* See here for more information about supported scenarios: https://aka.ms/msal4j-azure-regions
401
412
*
402
413
* @param val boolean (default is false)
@@ -410,13 +421,13 @@ public T autoDetectRegion(boolean val) {
410
421
/**
411
422
* Set the region that the library will use to format authorities in token requests. If given a valid Azure region,
412
423
* the library will attempt to make token requests at a regional ESTS-R endpoint rather than the global ESTS endpoint.
413
-
*
424
+
* <p>
414
425
* Regions must be valid Azure regions and their short names should be used, such as 'westus' for the West US Azure region,
415
426
* 'centralus' for the Central US Azure region, etc.
416
-
*
427
+
* <p>
417
428
* Although you can set a specific region here and enable autodetection with {@link AbstractClientApplicationBase#autoDetectRegion} at the same time
418
429
* the specific region set here will take priority over the autodetected region if there is a mismatch.
419
-
*
430
+
* <p>
420
431
* See here for more information about supported scenarios: https://aka.ms/msal4j-azure-regions
421
432
*
422
433
* @param val String region name
@@ -427,13 +438,15 @@ public T azureRegion(String val) {
427
438
returnself();
428
439
}
429
440
430
-
/** Historically, MSAL would connect to a central endpoint located at
431
-
``https://login.microsoftonline.com`` to acquire some metadata, especially when using an unfamiliar authority.
432
-
This behavior is known as Instance Discovery.
433
-
This parameter defaults to true, which enables the Instance Discovery.
434
-
If you do not know some authorities beforehand,
435
-
yet still want MSAL to accept any authority that you will provide,
436
-
you can use a ``False`` to unconditionally disable Instance Discovery. */
441
+
/**
442
+
* Historically, MSAL would connect to a central endpoint located at
443
+
* ``https://login.microsoftonline.com`` to acquire some metadata, especially when using an unfamiliar authority.
444
+
* This behavior is known as Instance Discovery.
445
+
* This parameter defaults to true, which enables the Instance Discovery.
446
+
* If you do not know some authorities beforehand,
447
+
* yet still want MSAL to accept any authority that you will provide,
448
+
* you can use a ``False`` to unconditionally disable Instance Discovery.
0 commit comments