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
Copy file name to clipboardExpand all lines: msal-javascript-conceptual/browser/access-token-proof-of-possession.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -171,4 +171,4 @@ Unlike other cache items, `Access Tokens` are saved to the cache asynchronously.
171
171
172
172
## Code samples
173
173
174
-
*[JavaScript SPA acquiring PoP tokens](../../../samples/msal-browser-samples/VanillaJSTestApp2.0/app/pop)
174
+
*[JavaScript SPA acquiring PoP tokens](https://github.com/AzureAD/microsoft-authentication-library-for-js/tree/dev/samples/msal-browser-samples/VanillaJSTestApp2.0/app/pop)
> This is the platform-specific Accounts documentation for `@azure/msal-browser`. For the general documentation of the `AccountInfo` object structure, please visit the `@azure/msal-common`[Accounts document](../../msal-common/docs/Accounts.md).
16
-
17
-
## Usage
18
-
19
-
The `@azure/msal-browser` library provides the following APIs to access cached accounts:
15
+
This is the platform-specific Accounts documentation for the `@azure/msal-browser` library, which provides the following APIs to access cached accounts:
20
16
21
17
-`getAllAccounts()`: returns all the accounts currently in the cache. Supports an optional filter to return a specific set of accounts. An application must choose an account to acquire tokens silently.
22
18
-`getAccount()`: returns the first cached account that matches the filter passed in. The order in which accounts are read from the cache is arbitrary and there is no guarantee that the first account in the filtered list will be the same for any two calls of `getAccount`. As explained below, increasing the number of filter attributes will provide more exact matches.
@@ -171,8 +167,8 @@ Note: As of version 2.16.0 the active account is stored in the cache ___location co
171
167
172
168
## Notes
173
169
174
-
- The current msal-browser default [sample](../../../samples/msal-browser-samples/VanillaJSTestApp2.0) has a working single account scenario.
175
-
- If you have a multiple accounts scenario, please modify the [sample](../../../samples/msal-browser-samples/VanillaJSTestApp2.0/app/default/auth.js) (in `handleResponse()`) to list all cached accounts and choose a specific account.
170
+
- The current msal-browser default [sample](https://github.com/AzureAD/microsoft-authentication-library-for-js/tree/dev/samples/msal-browser-samples/VanillaJSTestApp2.0/) has a working single account scenario.
171
+
- If you have a multiple accounts scenario, please modify the [sample](https://github.com/AzureAD/microsoft-authentication-library-for-js/tree/dev/samples/msal-browser-samples/VanillaJSTestApp2.0/app/default/auth.js) (in `handleResponse()`) to list all cached accounts and choose a specific account.
176
172
- If an application wants to retrieve an account based on the `username`, it needs to save the `username` (from the response of a `login` API for a specific user) prior to using `getAccountByUsername()` API.
177
173
-`getAllAccounts()` will return multiple accounts if you have made several interactive token requests and the user has selected different accounts in two or more of those interactions. You may need to pass `prompt: "select_account"` or `prompt: "login"` to the interactive acquireToken or login API in order for AAD to display the account selection screen after the first interaction.
178
174
- The account APIs return local account state and do not necessarily reflect server state. They return accounts that have previously signed into this app using MSAL.js and the server session may or may not still be active.
|`clientId`| App ID of your application. Can be found in your [portal registration](../README#prerequisites). | UUID/GUID | None. This parameter is required in order for MSAL to perform any actions. |
91
+
|`clientId`| App ID of your application. Can be found in your Azure Portal app registration pane| UUID/GUID | None. This parameter is required in order for MSAL to perform any actions. |
92
92
|`authority`| URI of the tenant to authenticate and authorize with. Usually takes the form of `https://{uri}/{tenantid}` (see [Authority](../../msal-common/docs/authority.md)) | String in URI format with tenant - `https://{uri}/{tenantid}`|`https://login.microsoftonline.com/common`|
93
93
|`knownAuthorities`| An array of URIs that are known to be valid. Used in B2C scenarios. | Array of strings in URI format | Empty array `[]`|
94
-
|`cloudDiscoveryMetadata`| A string containing the cloud discovery response. Used in AAD scenarios. See [Performance](../../msal-common/docs/performance.md) for more info | string | Empty string `""`|
95
-
|`authorityMetadata`| A string containing the .well-known/openid-configuration endpoint response. See [Performance](../../msal-common/docs/performance.md) for more info | string | Empty string `""`|
94
+
|`cloudDiscoveryMetadata`| A string containing the cloud discovery response. Used in AAD scenarios. | string | Empty string `""`|
95
+
|`authorityMetadata`| A string containing the .well-known/openid-configuration endpoint response. | string | Empty string `""`|
96
96
|`redirectUri`| URI where the authorization code response is sent back to. Whatever ___location is specified here must have the MSAL library available to handle the response. | String in absolute or relative URI format | Login request page (`window.___location.href` of page which made auth request) |
97
97
|`postLogoutRedirectUri`| URI that is redirected to after a logout() call is made. | String in absolute or relative URI format. Pass `null` to disable post logout redirect. | Login request page (`window.___location.href` of page which made auth request) |
98
98
|`navigateToLoginRequestUrl`| If `true`, will navigate back to the original request ___location before processing the authorization code response. If the `redirectUri` is the same as the original request ___location, this flag should be set to false. | boolean |`true`|
99
-
|`clientCapabilities`| Array of capabilities to be added to all network requests as part of the `xms_cc` claims request (see: [Client capability in MSAL](../../msal-common/docs/client-capability.md)) | Array of strings |[]|
99
+
|`clientCapabilities`| Array of capabilities to be added to all network requests as part of the `xms_cc` claims request | Array of strings |[]|
100
100
|`protocolMode`| Enum representing the protocol mode to use. If `"AAD"`, will function on the OIDC-compliant AAD v2 endpoints; if `"OIDC"`, will function on other OIDC-compliant endpoints. | string |`"AAD"`|
101
101
|`azureCloudOptions`| A defined set of azure cloud options for developers to default to their specific cloud authorities, for specific clouds supported please refer to the [AzureCloudInstance](https://aka.ms/msaljs/azure_cloud_instance)|[AzureCloudOptions](https://azuread.github.io/microsoft-authentication-library-for-js/ref/modules/_azure_msal_common.html#azurecloudoptions)|[AzureCloudInstance.None](msaljs/azure_cloud_instance)|
102
102
|`skipAuthorityMetadataCache`| A flag to choose whether to use the local metadata cache during authority initialization. Metadata cache would be used if no authority metadata is provided and before a network call for metadata has been made (see [Authority](../../msal-common/docs/authority.md)) | boolean |`false`|
@@ -126,7 +126,7 @@ See [Caching in MSAL](./caching.md) for more.
126
126
|`asyncPopups`| Sets whether popups are opened asynchronously. When set to false, blank popups are opened before anything else happens. When set to true, popups are opened when making the network request. Can be set to true for scenarios where `about:blank` is not supported, e.g. desktop apps or progressive web apps | boolean |`false`|
127
127
|`allowRedirectInIframe`| By default, MSAL will not allow redirect operations to be initiated when the application is inside an iframe. Set this flag to `true` to remove this check. | boolean |`false`|
128
128
|`cryptoOptions`| Config object for crypto operations in the browser. | See [below](#crypto-config-options.)| See [below](#crypto-config-options.)|
129
-
|`pollIntervalMilliseconds`| Interval of time in milliseconds between polls of popup URL hash during authenticaiton. | integer (milliseconds) |`30`|
129
+
|`pollIntervalMilliseconds`| Interval of time in milliseconds between polls of popup URL hash during authentication. | integer (milliseconds) |`30`|
0 commit comments