Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: AzureAD/microsoft-authentication-library-for-js
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: 3ff9f0af4449162b7a124975bafda484b8747afd
Choose a base ref
...
head repository: AzureAD/microsoft-authentication-library-for-js
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: 6ca3a6b3be34b8607c9558b7d4c0f494e8c40440
Choose a head ref
  • 3 commits
  • 39 files changed
  • 4 contributors

Commits on Aug 15, 2023

  1. August 2023 LTS Post-Release (#6344)

    This PR:
    - Updates package-lock.json files with the newly published LTS versions
    - Updates CDN usage docs and SRI Hashes
    
    ---------
    
    Co-authored-by: Thomas Norling <thomas.norling@microsoft.com>
    hectormmg and tnorling authored Aug 15, 2023

    Verified

    This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
    Copy the full SHA
    55a0972 View commit details

Commits on Aug 24, 2023

  1. Clear claims cache for apps that switched their cache preferences [LT…

    …S] (#6356)
    
    Some apps fetch tokens with high frequency and changing claims (new
    claim per request). Prior to #6187, these tokens over flowed the local
    cache. However, there is still the issue of stale tokens to be cleared
    when the `claimsBasedCachingEnabled` feature is set to false, which is
    not addressed.
    
    This PR adds a new utility function `clearTokensAndKeysWithClaims()`
    which will be triggered when the application is `initialized` to clear
    any old tokens cached with claims.
    
    The initial choice is to clear the cache at token acquisition. However
    apps facing this issue will not be able to fetch tokens since the
    `tokenKeys` cache entry is already large and freezes the app. Hence the
    choice of adding this when the app is initialized and the extra
    requirement of any application on the msal v2 to specifically call
    `msal.initialize()` as a pre-requisite.
    
    Applications are mandated to call `initialize()` for `msal v3` and we
    are defaulting to `claimsBasedCachingEnabled: false` in v3. Hoping both
    these settings will mitigate this issue from day one in the new version.
    
    So here is the guidance:
    
    `msal-browser v2`: App needs to explicitly set
    `claimsBasedCachingEnabled: false` and call `initialize()` to use msal
    to mitigate this issue.
    `msal-browser v3`: MSAL JS should handle this in the back ground.
    
    P.S: Currently this approach is in test and once approved will push the
    changes to v3.
    
    ---------
    
    Co-authored-by: Thomas Norling <thomas.norling@microsoft.com>
    sameerag and tnorling authored Aug 24, 2023

    Verified

    This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
    Copy the full SHA
    f85761c View commit details
  2. msal-lts release 08/24

    lalimasharda committed Aug 24, 2023
    Copy the full SHA
    6ca3a6b View commit details
Loading