npm - @azure/msal-angular - Versions diffs - 4.0.13 → 4.0.15 - Mend

@azure/msal-angular 4.0.13 → 4.0.15

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (89) hide show

package/IMsalService.d.ts +17 -0
package/README.md +1 -1
package/constants.d.ts +5 -0
package/esm2020/IMsalService.mjs +6 -0
package/esm2020/azure-msal-angular.mjs +5 -0
package/esm2020/constants.mjs +10 -0
package/esm2020/msal.broadcast.config.mjs +6 -0
package/esm2020/msal.broadcast.service.mjs +66 -0
package/esm2020/msal.guard.config.mjs +6 -0
package/esm2020/msal.guard.mjs +218 -0
package/esm2020/msal.interceptor.config.mjs +6 -0
package/esm2020/msal.interceptor.mjs +270 -0
package/esm2020/msal.module.mjs +46 -0
package/esm2020/msal.navigation.client.mjs +53 -0
package/esm2020/msal.redirect.component.mjs +31 -0
package/esm2020/msal.service.mjs +88 -0
package/esm2020/packageMetadata.mjs +4 -0
package/esm2020/public-api.mjs +18 -0
package/fesm2015/azure-msal-angular.mjs +762 -0
package/fesm2015/azure-msal-angular.mjs.map +1 -0
package/fesm2020/azure-msal-angular.mjs +758 -0
package/fesm2020/azure-msal-angular.mjs.map +1 -0
package/index.d.ts +5 -0
package/msal.broadcast.config.d.ts +3 -0
package/msal.broadcast.service.d.ts +19 -0
package/msal.guard.config.d.ts +9 -0
package/msal.guard.d.ts +43 -0
package/msal.interceptor.config.d.ts +13 -0
package/msal.interceptor.d.ts +70 -0
package/msal.module.d.ts +13 -0
package/msal.navigation.client.d.ts +19 -0
package/msal.redirect.component.d.ts +15 -0
package/msal.service.d.ts +33 -0
package/package.json +26 -56
package/packageMetadata.d.ts +2 -0
package/{src/public-api.ts → public-api.d.ts} +17 -35
package/.beachballrc +0 -3
package/.editorconfig +0 -16
package/.eslintrc.json +0 -3
package/CHANGELOG.json +0 -2315
package/CHANGELOG.md +0 -869
package/FAQ.md +0 -182
package/angular.json +0 -51
package/docs/angular-universal.md +0 -64
package/docs/configuration.md +0 -609
package/docs/errors.md +0 -89
package/docs/events.md +0 -262
package/docs/initialization.md +0 -206
package/docs/known-issues.md +0 -19
package/docs/logging.md +0 -47
package/docs/msal-guard.md +0 -208
package/docs/msal-interceptor.md +0 -160
package/docs/multi-tenant.md +0 -90
package/docs/performance.md +0 -50
package/docs/public-apis.md +0 -29
package/docs/redirects.md +0 -257
package/docs/security.md +0 -4
package/docs/ssosilent.md +0 -84
package/docs/v0-v1-upgrade-guide.md +0 -61
package/docs/v1-v2-upgrade-guide.md +0 -70
package/docs/v2-v3-upgrade-guide.md +0 -52
package/docs/v3-v4-upgrade-guide.md +0 -36
package/karma.conf.js +0 -44
package/ng-package.json +0 -7
package/src/IMsalService.ts +0 -34
package/src/constants.ts +0 -20
package/src/msal.broadcast.config.ts +0 -8
package/src/msal.broadcast.service.spec.ts +0 -471
package/src/msal.broadcast.service.ts +0 -84
package/src/msal.guard.config.ts +0 -27
package/src/msal.guard.spec.ts +0 -525
package/src/msal.guard.ts +0 -290
package/src/msal.interceptor.config.ts +0 -39
package/src/msal.interceptor.spec.ts +0 -1168
package/src/msal.interceptor.ts +0 -388
package/src/msal.module.ts +0 -51
package/src/msal.navigation.client.spec.ts +0 -96
package/src/msal.navigation.client.ts +0 -59
package/src/msal.redirect.component.spec.ts +0 -64
package/src/msal.redirect.component.ts +0 -26
package/src/msal.service.spec.ts +0 -468
package/src/msal.service.ts +0 -104
package/src/packageMetadata.ts +0 -3
package/src/test.ts +0 -19
package/tsconfig.json +0 -25
package/tsconfig.lib.json +0 -27
package/tsconfig.lib.prod.json +0 -10
package/tsconfig.spec.json +0 -17
package/typedoc.json +0 -10

package/docs/redirects.md DELETED Viewed

@@ -1,257 +0,0 @@
-# Using redirects in MSAL Angular
-When using redirects with MSAL, it is **mandatory** to handle redirects with either the `MsalRedirectComponent` or `handleRedirectObservable`. While we recommend `MsalRedirectComponent` as the best approach, both approaches are detailed below.
-Note that specific guidance has been added for using MSAL Angular with Angular standalone components below.
-1. [`MsalRedirectComponent`](#msalredirectcomponent-a-dedicated-handleredirectobservable-component)
-1. [Subscribing to `handleRedirectObservable` manually](#subscribing-to-handleredirectobservable-manually)
-1. [Redirects with standalone components](#redirects-with-standalone-components)
-## `MsalRedirectComponent`: A dedicated `handleRedirectObservable` component
-This is our recommended approach for handling redirects:
-- `@azure/msal-angular` provides a dedicated redirect component that can be imported  into your application. We recommend importing the `MsalRedirectComponent` and bootstrapping this alongside `AppComponent` in your application on the `app.module.ts`, as this will handle all redirects without your components needing to subscribe to `handleRedirectObservable()` manually.
-- Pages that wish to perform functions following redirects (e.g. user account functions, UI changes, etc) should subscribe to the `inProgress$` observable, filtering for `InteractionStatus.None`. This will ensure that there are no interactions in progress when performing the functions. Note that the last / most recent `InteractionStatus` will also be available when subscribing to the `inProgress$` observable. Please see our documentation on [events](https://github.com/AzureAD/microsoft-authentication-library-for-js/blob/dev/lib/msal-angular/docs/events.md#the-inprogress-observable) for more information on checking for interactions.
-- If you do not wish to use the `MsalRedirectComponent`, you **must** handle redirects with `handleRedirectObservable()` yourself, as laid out in the approach below.
-- See our [Angular 15 sample](https://github.com/AzureAD/microsoft-authentication-library-for-js/blob/dev/samples/msal-angular-samples/angular-modules-sample/src/app/app.module.ts#L110) for an example of this approach.
-Note that although this is our recommendation for most Angular applications, this approach may not work with Angular standalone components. See the section on [redirects with standalone components below](#redirects-with-standalone-components) for further guidance.
-msal.redirect.component.ts
-```js
-// This component is part of @azure/msal-angular and can be imported and bootstrapped
-import { Component, OnInit } from "@angular/core";
-import { MsalService } from "./msal.service.ts";
-@Component({
-  selector: 'app-redirect', // Selector to be added to index.html
-  template: ''
-})
-export class MsalRedirectComponent implements OnInit {
-  constructor(private authService: MsalService) { }
-  ngOnInit(): void {
-      this.authService.handleRedirectObservable().subscribe();
-  }
-}
-```
-index.html
-```js
-<body>
-  <app-root></app-root>
-  <app-redirect></app-redirect> <!-- Selector for additional bootstrapped component -->
-</body>
-```
-app.module.ts
-```js
-import { BrowserModule } from '@angular/platform-browser';
-import { BrowserAnimationsModule } from '@angular/platform-browser/animations';
-import { NgModule } from '@angular/core';
-import { MatButtonModule } from '@angular/material/button';
-import { MatToolbarModule } from '@angular/material/toolbar';
-import { MatListModule } from '@angular/material/list';
-import { AppRoutingModule } from './app-routing.module';
-import { AppComponent } from './app.component';
-import { HomeComponent } from './home/home.component';
-import { ProfileComponent } from './profile/profile.component';
-import { HTTP_INTERCEPTORS, HttpClientModule } from '@angular/common/http';
-import { IPublicClientApplication, PublicClientApplication, InteractionType, BrowserCacheLocation, LogLevel } from '@azure/msal-browser';
-import { MsalGuard, MsalInterceptor, MsalBroadcastService, MsalInterceptorConfiguration, MsalModule, MsalService, MSAL_GUARD_CONFIG, MSAL_INSTANCE, MSAL_INTERCEPTOR_CONFIG, MsalGuardConfiguration, MsalRedirectComponent } from '@azure/msal-angular'; // Redirect component imported from msal-angular
-export function loggerCallback(logLevel: LogLevel, message: string) {
-  console.log(message);
-}
-export function MSALInstanceFactory(): IPublicClientApplication {
-  return new PublicClientApplication({
-    auth: {
-      clientId: 'b5c2e510-4a17-4feb-b219-e55aa5b74144',
-      redirectUri: 'http://localhost:4200',
-      postLogoutRedirectUri: 'http://localhost:4200'
-    },
-    cache: {
-      cacheLocation: BrowserCacheLocation.LocalStorage
-    },
-    system: {
-      loggerOptions: {
-        loggerCallback,
-        logLevel: LogLevel.Info,
-        piiLoggingEnabled: false
-      }
-    }
-  });
-}
-export function MSALInterceptorConfigFactory(): MsalInterceptorConfiguration {
-  const protectedResourceMap = new Map<string, Array<string>>();
-  protectedResourceMap.set('https://graph.microsoft.com/v1.0/me', ['user.read']);
-  return {
-    interactionType: InteractionType.Redirect,
-    protectedResourceMap
-  };
-}
-export function MSALGuardConfigFactory(): MsalGuardConfiguration {
-  return { interactionType: InteractionType.Redirect };
-}
-@NgModule({
-  declarations: [
-    AppComponent,
-    HomeComponent,
-    ProfileComponent
-  ],
-  imports: [
-    BrowserModule,
-    BrowserAnimationsModule,
-    AppRoutingModule,
-    MatButtonModule,
-    MatToolbarModule,
-    MatListModule,
-    HttpClientModule,
-    MsalModule
-  ],
-  providers: [
-    {
-      provide: HTTP_INTERCEPTORS,
-      useClass: MsalInterceptor,
-      multi: true
-    },
-    {
-      provide: MSAL_INSTANCE,
-      useFactory: MSALInstanceFactory
-    },
-    {
-      provide: MSAL_GUARD_CONFIG,
-      useFactory: MSALGuardConfigFactory
-    },
-    {
-      provide: MSAL_INTERCEPTOR_CONFIG,
-      useFactory: MSALInterceptorConfigFactory
-    },
-    MsalService,
-    MsalGuard,
-    MsalBroadcastService
-  ],
-  bootstrap: [AppComponent, MsalRedirectComponent] // Redirect component bootstrapped here
-})
-export class AppModule { }
-```
-app.component.ts
-```js
-import { Component, OnInit, Inject, OnDestroy } from '@angular/core';
-import { MsalBroadcastService, InteractionStatus } from '@azure/msal-angular';
-import { Subject } from 'rxjs';
-import { filter, takeUntil } from 'rxjs/operators';
-@Component({
-  selector: 'app-root',
-  templateUrl: './app.component.html',
-  styleUrls: ['./app.component.css']
-})
-export class AppComponent implements OnInit, OnDestroy {
-  private readonly _destroying$ = new Subject<void>();
-  constructor(
-    private msalBroadcastService: MsalBroadcastService
-  ) {}
-  ngOnInit(): void {
-    this.msalBroadcastService.inProgress$
-      .pipe(
-        filter((status: InteractionStatus) => status === InteractionStatus.None),
-        takeUntil(this._destroying$)
-      )
-      .subscribe(() => {
-        // Do user account/UI functions here
-      })
-  }
-```
-## Subscribing to `handleRedirectObservable` manually
-This is not our recommended approach, but if you are unable to bootstrap the `MsalRedirectComponent`, you **must** handle redirects using the `handleRedirectObservable` as follows:
-- `handleRedirectObservable()` should be subscribed to on **every** page to which a redirect may occur. Pages protected by the MSAL Guard do not need to subscribe to `handleRedirectObservable()`, as redirects are processed in the Guard.
-- Accessing or performing any action related to user accounts should not be done until `handleRedirectObservable()` is complete, as it may not be fully populated until then. Additionally, if interactive APIs are called while `handleRedirectObservables()` is in progress, it will result in an `interaction_in_progress` error. See our document on [events](https://github.com/AzureAD/microsoft-authentication-library-for-js/blob/dev/lib/msal-angular/docs/events.md#the-inprogress-observable) for more information on checking for interactions, and our document on [errors](https://github.com/AzureAD/microsoft-authentication-library-for-js/blob/dev/lib/msal-angular/docs/errors.md) for details about the `interaction_in_progress` error.
-- See our [older MSAL Angular v2 Angular 9 sample](https://github.com/AzureAD/microsoft-authentication-library-for-js/tree/msal-lts/samples/msal-angular-v2-samples/angular9-v2-sample-app) for examples of this approach.
-Example of home.component.ts file:
-```js
-import { Component, OnInit } from '@angular/core';
-import { MsalBroadcastService, MsalService } from '@azure/msal-angular';
-import { AuthenticationResult } from '@azure/msal-browser';
-@Component({
-  selector: 'app-home',
-  templateUrl: './home.component.html',
-  styleUrls: ['./home.component.css']
-})
-export class HomeComponent implements OnInit {
-  constructor(private authService: MsalService) { }
-  ngOnInit(): void {
-    this.authService.handleRedirectObservable().subscribe({
-      next: (result: AuthenticationResult) => {
-        // Perform actions related to user accounts here
-      },
-      error: (error) => console.log(error)
-    });
-  }
-}
-```
-## Redirects with standalone components
-As many Angular applications using standalone components are unable to bootstrap the `MsalRedirectComponent`, `handleRedirectObservable` must be subscribed to directly. Our recommendation is to subscribe to it in the `app.component.ts` file.
-- Depending on your application architecture, you may have to subscribe to `handleRedirectObservable()` in other areas as well.
-- Checking for interactions in progress still applies, please see our document on [events](https://github.com/AzureAD/microsoft-authentication-library-for-js/blob/dev/lib/msal-angular/docs/events.md#the-inprogress-observable) for more information on checking for interactions.
-- See our [Angular standalone sample](https://github.com/AzureAD/microsoft-authentication-library-for-js/blob/dev/samples/msal-angular-samples/angular-standalone-sample) for examples of this approach.
-Example of `app.component.ts` file
-```js
-import { Component, OnInit, Inject } from '@angular/core';
-import { CommonModule } from '@angular/common';
-import { RouterModule} from '@angular/router';
-import { MsalService, MsalBroadcastService, MSAL_GUARD_CONFIG, MsalGuardConfiguration } from '@azure/msal-angular';
-@Component({
-    selector: 'app-root',
-    templateUrl: './app.component.html',
-    styleUrls: ['./app.component.css'],
-    standalone: true,
-    imports: [CommonModule, RouterModule]
-})
-export class AppComponent implements OnInit {
-  constructor(
-    @Inject(MSAL_GUARD_CONFIG) private msalGuardConfig: MsalGuardConfiguration,
-    private authService: MsalService,
-    private msalBroadcastService: MsalBroadcastService
-  ) {}
-  ngOnInit(): void {
-    this.authService.handleRedirectObservable().subscribe(); // Subscribing to handleRedirectObservable before any other functions both initializes the application and ensures redirects are handled
-  }
-}
-```

package/docs/security.md DELETED Viewed

@@ -1,4 +0,0 @@
-# Security
-Tokens are accessible from JavaScript since MSAL is using HTML5 storage. Default storage option is `sessionStorage`, which keeps the tokens per session. You should ask user to login again for important operations on your app.
-You should protect your site for XSS. Please check the article here: [Cross Site Scripting Prevention Cheat Sheet](<https://cheatsheetseries.owasp.org/cheatsheets/Cross_Site_Scripting_Prevention_Cheat_Sheet.html>)

package/docs/ssosilent.md DELETED Viewed

@@ -1,84 +0,0 @@
-# Silent login with ssoSilent()
-If you already have a session that exists with the authentication server, you can use the `ssoSilent()` API to make a request for tokens without interaction.
-## With User Hint
-If you already have the user's sign-in information, you can pass this into the API to improve performance and ensure that the authorization server will look for the correct account session. You can pass one of the following into the request object in order to successfully obtain a token silently.
-- `account` (which can be retrieved using on of the [account APIs](./accounts.md))
-- `sid` (which can be retrieved from the `idTokenClaims` of an `account` object)
-- `login_hint` (which can be retrieved from the account object `username` property or the `upn` claim in the ID token)
-Passing an account will look for sid in the token claims, then fall back to loginHint (if provided) or account username.
-```js
-const silentRequest: SsoSilentRequest = {
-    scopes: ["User.Read", "Mail.Read"],
-    loginHint: "user@contoso.com"
-};
-this.authService.ssoSilent(silentRequest)
-    .subscribe({
-        next: (result) => console.log("Success!"), // Handle result
-        error: (error) => console.log(error) // Handle error
-    });
-```
-## Without User Hint
-If there is not enough information available about the user, you can attempt to use the `ssoSilent` API **without** passing an `account`, `sid` or `login_hint`.
-```javascript
-const silentRequest = {
-    scopes: ["User.Read", "Mail.Read"]
-};
-```
-However, be aware that if your application has code paths for multiple users in a single browser session, or if the user has multiple accounts for that single browser session, then there is a higher likelihood of silent sign-in errors. You may see the following error show up in the event of multiple account sessions found by the authorization server:
-```txt
-InteractionRequiredAuthError: interaction_required: AADSTS16000: Either multiple user identities are available for the current request or selected account is not supported for the scenario.
-```
-This indicates that the server could not determine which account to sign into, and will require either one of the parameters above (`account`, `login_hint`, `sid`) or an interactive sign-in to choose the account.
-## Handling Failures
-If ssoSilent() fails, we recommend handling this error by logging in interactively. Here is an example of ssoSilent() being used in an application's `app.component.ts`:
-```js
-import { Component, OnInit } from '@angular/core';
-import { MsalService } from '@azure/msal-angular';
-import { SilentRequest, SsoSilentRequest } from '@azure/msal-browser';
-@Component({
-  selector: 'app-root',
-  templateUrl: './app.component.html',
-  styleUrls: ['./app.component.css']
-})
-export class AppComponent implements OnInit {
-  constructor(
-    private authService: MsalService,
-  ) {}
-  ngOnInit(): void {
-    const silentRequest: SsoSilentRequest = {
-      scopes: ["User.Read"],
-      loginHint: "user@contoso.com"
-    }
-    this.authService.ssoSilent(silentRequest)
-      .subscribe({
-        next: (result: AuthenticationResult) => {
-          console.log("SsoSilent succeeded!"); // Handle result
-        },
-        error: (error) => {
-          this.authService.loginRedirect(); // Handle error by logging in interactively
-        }
-      });
-  }
-}
-```

package/docs/v0-v1-upgrade-guide.md DELETED Viewed

@@ -1,61 +0,0 @@
-# Upgrading from MSAL Angular v0 to v1
-MSAL Angular v1 brings our Angular wrapper up-to-date with the latest version of MSAL core, and with out-of-the-box support for modern versions of Angular (6+) and rxjs (6).
-This guide will demonstrate changes needed to migrate an existing application from `@azure/msal-angular@0.x` to `@azure/msal-angular@1.0.0`.
-A detailed list of changes can be found in the [CHANGELOG](https://github.com/AzureAD/microsoft-authentication-library-for-js/blob/dev/lib/msal-angular/CHANGELOG.md).
-Documentation for MSAL Angular v1 can be found [here](https://github.com/AzureAD/microsoft-authentication-library-for-js/tree/msal-lts/lib/msal-angular/docs/v1-docs/).
-## Installation
-The first fundamental change to MSAL Angular is that the core `msal` package is no longer a regular dependency, and instead a [peer dependency](https://nodejs.org/en/blog/npm/peer-dependencies/). This means your application must also include `msal` as a normal dependency, instead of relying on MSAL Angular to include it. This allows for your application to either use the latest version of `msal` (recommended), or you can pick a custom version/range, while still using the latest version of MSAL Angular itself. Note, you should still provide a version that satisfies the semver range provided for the peer dependency, or else MSAL Angular may not function as intended.
-Steps:
-1. Install `msal` and `@azure/msal-angular`: `npm install msal@beta @azure/msal-angular@beta`.
-## Breaking changes in MSAL.js v1
-`msal@1` includes a number of breaking changes from `msal@0.2.x`. Many of these should be abstracted away from your application, but there are a few which will require code changes.
-### MsalModule.forRoot now takes two arguments.
-Previously, MSAL Angular accepted one configuration object via `MsalModule.forRoot()`. To more closely align with `msal@1` and to provide more flexibility to MSAL Angular, this has been split into two objects, one for the core library and one for the wrapper.
-Steps:
-1. The first argument is the configuration object, which is the [same `Configuration` object](https://github.com/AzureAD/microsoft-authentication-library-for-js/blob/msal-lts/lib/msal-core/src/Configuration.ts) you would pass to `msal`.
-2. The second argument is a [`MsalAngularConfiguration object`](https://github.com/AzureAD/microsoft-authentication-library-for-js/blob/msal-angular-v1/lib/msal-angular/src/msal-angular.configuration.ts), containing the values for `consentScopes`, `popUp`, `extraQueryParameters`, and `protectedResourceMap`. `unprotectedResources` has been deprecated.
-See the [sample](https://github.com/AzureAD/microsoft-authentication-library-for-js/blob/msal-lts/samples/msal-angular-samples/angular6-sample-app/src/app/app.module.ts) for an example of how to pass these configuration objects.
-### Mitigations for AOT mode errors
-The new `msal` configuration object takes a function for `system.logger` and `framework.protectedResourceMap`, which does not work properly when running in `aot` mode. There are now two workarounds available:
-1. `protectedResourceMap` has been moved to `MsalAngularConfiguration` object, and can be passed as `[string, string[]][]` or as a `Map`. `framework.protectedResourceMap` still works, but has been deprecated. See the [updated samples](https://github.com/AzureAD/microsoft-authentication-library-for-js/blob/msal-lts/samples/msal-angular-samples/angular6-sample-app/src/app/app.module.ts) for usage.
-2. `logger` can now be set dynamically by using `MsalService.setLogger()`. See the [updated samples](https://github.com/AzureAD/microsoft-authentication-library-for-js/blob/msal-lts/samples/msal-angular-samples/angular6-sample-app/src/app/app.component.ts) for usage.
-### Other breaking changes
-* The `acquireToken` and `login` methods now take a single `AuthenticationParameters` object as parameters.
-* `getUser()` is now `getAccount()`.
-* Broadcast events now emit objects, instead of just strings.
-* Applications using `Redirect` methods must implement the `handleRedirectCallback` method (and have it run on every page load), which will capture the result of redirect operations. See the [Angular sample](https://github.com/AzureAD/microsoft-authentication-library-for-js/blob/msal-lts/samples/msal-angular-samples/angular6-sample-app/src/app/app.component.ts) for an example of how to implement.
-## Angular 6+ and rxjs@6
-MSAL Angular now expects that your application is built with `@angular/core@>=6`, `@angular/common@>=6`, `rxjs@6`. And `rxjs-compat` is no longer required.
-Steps:
-1. Install newer versions of Angular and rxjs: `npm install @angular/core @angular/common rxjs`
-2. Uninstall `rxjs-compat` (assuming it is not needed for other libraries): `npm uninstall rxjs-compat`
-## Samples
-We have put together basic sample applications for Angular 6, 7, 8, and 9. These samples demonstrate basic configuration and usage, and will be improved and added to incrementally. We also are planning to include more samples for more scenarios and use cases.
-* [Angular 6](https://github.com/AzureAD/microsoft-authentication-library-for-js/tree/msal-lts/samples/msal-angular-samples/angular6-sample-app)
-* [Angular 7](https://github.com/AzureAD/microsoft-authentication-library-for-js/tree/msal-lts/samples/msal-angular-samples/angular7-sample-app)
-* [Angular 8](https://github.com/AzureAD/microsoft-authentication-library-for-js/tree/msal-lts/samples/msal-angular-samples/angular8-sample-app)
-* [Angular 9](https://github.com/AzureAD/microsoft-authentication-library-for-js/tree/msal-lts/samples/msal-angular-samples/angular9-sample-app)

package/docs/v1-v2-upgrade-guide.md DELETED Viewed

@@ -1,70 +0,0 @@
-# Upgrading from MSAL Angular v1 to v2
-MSAL Angular v2 brings our Angular wrapper up-to-date with the latest version of MSAL common, and with out-of-the-box support for modern versions of Angular (9 - 12) and rxjs (6).
-This guide will demonstrate changes needed to migrate an existing application from `@azure/msal-angular` v1 to v2.
-Documentation specifically for MSAL Angular v2 can be found [here](https://github.com/AzureAD/microsoft-authentication-library-for-js/tree/msal-lts/lib/msal-angular/docs/v2-docs/).
-## Installation
-The first fundamental change to MSAL Angular v2 is that is no longer uses the core `msal` package, but wraps the `@azure/msal-browser` package as a [peer dependency](https://nodejs.org/en/blog/npm/peer-dependencies/).
-First, uninstall any previous versions of MSAL currently being used.
-To install `@azure/msal-browser` and `@azure/msal-angular`:
-```
-npm install @azure/msal-browser @azure/msal-angular@latest
-```
-## Breaking changes in `@azure/msal-browser@2`
-`@azure/msal-browser@2` includes a number of breaking changes from `msal@1.x`. Many of these should be abstracted away from your application, but there are a few which will require code changes.
-### MsalModule.forRoot now takes three arguments
-Previously, `@azure/msal-angular` accepted two configuration objects via `MsalModule.forRoot()`, one for the core library, and one for `@azure/msal-angular`. This has been changed to take in an instance of MSAL, as well as two Angular-specific configuration objects.
-1. The first argument is the MSAL instance. This can be provided as a factory which instantiates MSAL, or by passing the instance of MSAL in with configurations.
-2. The second argument is a [`MsalGuardConfiguration`](https://github.com/AzureAD/microsoft-authentication-library-for-js/blob/msal-lts/lib/msal-angular/src/msal.guard.config.ts) object, which specifies the `interactionType` as well as an optional `authRequest` and an optional `loginFailedRoute`.
-3. The third argument is a [`MsalInterceptorConfiguration`](https://github.com/AzureAD/microsoft-authentication-library-for-js/blob/msal-lts/lib/msal-angular/src/msal.interceptor.config.ts) object, which contain the values for `interactionType`, a `protectedResourceMap`, and an optional `authRequest`. `unprotectedResourceMap` has been deprecated.
-See our [configuration doc](https://github.com/AzureAD/microsoft-authentication-library-for-js/blob/msal-lts/lib/msal-angular/docs/v2-docs/configuration.md) and specific docs for [MsalInterceptor](https://github.com/AzureAD/microsoft-authentication-library-for-js/blob/msal-lts/lib/msal-angular/docs/v2-docs/msal-interceptor.md) and [MsalGuard](https://github.com/AzureAD/microsoft-authentication-library-for-js/blob/msal-lts/lib/msal-angular/docs/v2-docs/msal-guard.md) for more information. You can also see our [updated samples](https://github.com/AzureAD/microsoft-authentication-library-for-js/blob/msal-lts/samples/msal-angular-v2-samples/angular10-sample-app/src/app/app.module.ts) for examples of how to pass these configuration objects.
-### Logger
-* The `logger` is now set through configurations for the MSAL instance, under `system.loggerOptions`, which include a `loggerCallback`, `piiLoggingEnabled` and `logLevel`, instead of an instance of a `logger`. The `logger` can also be set dynamically by using `MsalService.setLogger()`. See the [`logger documentation`](https://github.com/AzureAD/microsoft-authentication-library-for-js/blob/msal-lts/lib/msal-angular/docs/v2-docs/logging.md) for more information and [sample](https://github.com/AzureAD/microsoft-authentication-library-for-js/blob/msal-lts/samples/msal-angular-v2-samples/angular10-sample-app/src/app/app.module.ts) for usage.
-### API changes
-* The `acquireToken` and `login` methods now take different request objects as parameters. See the [msal.service.ts](https://github.com/AzureAD/microsoft-authentication-library-for-js/blob/msal-lts/lib/msal-angular/src/msal.service.ts) for details.
-* Broadcast events now emit an `EventMessage` object, instead of just strings. See the [Angular sample](https://github.com/AzureAD/microsoft-authentication-library-for-js/blob/msal-lts/samples/msal-angular-v2-samples/angular10-sample-app/src/app/app.component.ts) for an example of how to implement.
-* Applications using `Redirect` methods should import the `MsalRedirectComponent` and bootstrap along with `AppComponent` in their app.component.ts, which will handle all redirects. Applications are unable to do this should implement the `handleRedirectObservable` method (and have it run on every page load), which will capture the result of redirect operations. See the [redirect documentation](https://github.com/AzureAD/microsoft-authentication-library-for-js/tree/msal-lts/lib/msal-angular/docs/v2-docs/redirects.md) for more details.
-### MSAL Interceptor
-* Please our [MsalInterceptor doc](https://github.com/AzureAD/microsoft-authentication-library-for-js/blob/msal-lts/lib/msal-angular/docs/v2-docs/msal-interceptor.md) for more details on configuring the current `MsalInterceptor`, and differences between v1 and v2.
-### MSAL Guard
-* Please our [MsalGuard doc](https://github.com/AzureAD/microsoft-authentication-library-for-js/blob/msal-lts/lib/msal-angular/docs/v2-docs/msal-guard.md) for more details on configuring the current `MsalGuard`, and differences between v1 and v2.
-### Accounts
-* We recommend subscribing to the `inProgress$` observable and filtering for `InteractionStatus.None` before retrieving account information. This ensures that all interactions have completed before getting account information. See [our sample](https://github.com/AzureAD/microsoft-authentication-library-for-js/blob/msal-lts/samples/msal-angular-v2-samples/angular10-sample-app/src/app/app.component.ts#L27) for an example of this use.
-* When getting accounts, we recommend using `getAccountByHomeId()` and `getAccountByLocalId()`, available on the MSAL instance. `getAccount()` is now `getAccountByUsername()`, but should be a secondary choice, as it may be less reliable and is for convenience only.
-* `getAllAccounts()` is also available on the MSAL instance. Please see [docs](https://azuread.github.io/microsoft-authentication-library-for-js/ref/classes/_azure_msal_browser.publicclientapplication.html) for `@azure/msal-browser` for more details on account methods.
-* Additionally, you can now get and set active acccounts using `getActiveAccount()` and `setActiveAccount()`. See our [FAQ](https://github.com/AzureAD/microsoft-authentication-library-for-js/blob/msal-lts/lib/msal-angular/docs/v2-docs/FAQ.md#how-do-i-get-and-set-active-accounts) for more information.
-## Angular 9+ and rxjs@6
-MSAL Angular now expects that your application is built with `@angular/core@>=9`, `@angular/common@>=9`, `rxjs@6`. As with MSAL Angular v1, `rxjs-compat` is not required.
-Steps:
-1. Install newer versions of Angular and rxjs: `npm install @angular/core @angular/common rxjs`
-2. Uninstall `rxjs-compat` (assuming it is not needed for other libraries): `npm uninstall rxjs-compat`
-## Samples
-We have put together basic sample applications for Angular 9, 10, 11, and 12. These samples demonstrate basic configuration and usage, and will be improved and added to incrementally.
-See [here](https://github.com/AzureAD/microsoft-authentication-library-for-js/blob/msal-lts/samples/msal-angular-v2-samples/README.md) for a list of the MSAL Angular v2 samples and the features demonstrated.

package/docs/v2-v3-upgrade-guide.md DELETED Viewed

@@ -1,52 +0,0 @@
-# Upgrading from MSAL Angular v2 to v3
-MSAL Angular v3 brings our Angular wrapper up-to-date with the latest version of MSAL Browser, and with out-of-the-box support for Angular 15, 16, 17, 18 and rxjs 7.
-This guide will demonstrate changes needed to migrate an existing application from `@azure/msal-angular` v2 to v3.
-If you are migrating from `@azure/msal-angular` v1, please refer to the [v1-v2 migration guide](https://github.com/AzureAD/microsoft-authentication-library-for-js/tree/dev/lib/msal-angular/docs/v1-v2-upgrade-guide.md) first to migrate to MSAL v2.
-Please also see the [MSAL Browser Migration Doc](https://github.com/AzureAD/microsoft-authentication-library-for-js/tree/dev/lib/msal-browser/docs/v2-migration.md) for browser support and other key changes.
-## Breaking changes in `@azure/msal-angular@3`
-### Initialization
-#### Applications using redirects
-MSAL v3.x now requires initializing the application object. Initialization has been built into the `MsalRedirectComponent` and `handleRedirectObservable` API, and applications that have implemented redirect strategies do not have to make changes. Additional changes may need to be made if your application is using standalone components.
-See the [guide to redirects](https://github.com/AzureAD/microsoft-authentication-library-for-js/tree/dev/lib/msal-angular/docs/redirects.md) for details on handling redirects in your application.
-#### Applications using popups
-Due to initialization being built into `MsalRedirectComponent` and `handleRedirectObservable`, applications that only use popups will also have to either bootstrap the `MsalRedirectComponent` or call `handleRedirectObservable` manually once to initialize the application object.
-See the [guide to redirects](https://github.com/AzureAD/microsoft-authentication-library-for-js/tree/dev/lib/msal-angular/docs/redirects.md) for set up details.
-## Angular 15, 16, 17, 18 and rxjs@7
-MSAL Angular now expects that your application is built with:
-- `@angular/core@15` or `@angular/core@16` or `@angular/core@17` or `@angular/core@18`
-- `@angular/common@15` or `@angular/common@16` or `@angular/common@17` or `@angular/common@18`
-- `rxjs@7`
-Due to this change, MSAL Angular v3 is not backwards compatible with earlier versions of Angular and RxJS and you may need to update your application. Please follow the [Angular Update Guide](https://update.angular.io/) to update your application to Angular 15, 16, 17 or 18.
-As with MSAL Angular v2, `rxjs-compat` is not required.
-## Samples
-The following developer samples are now available:
-- [Angular 15 sample](https://github.com/AzureAD/microsoft-authentication-library-for-js/tree/v3-lts/samples/msal-angular-v3-samples/angular15-sample-app)
-- [Angular 16 sample](https://github.com/AzureAD/microsoft-authentication-library-for-js/tree/v3-lts/samples/msal-angular-v3-samples/angular16-sample-app)
-- [Angular 16 sample using B2C](https://github.com/AzureAD/microsoft-authentication-library-for-js/tree/v3-lts/samples/msal-angular-v3-samples/angular-b2c-sample-app)
-- [Angular 16 sample using Angular standalone components](https://github.com/AzureAD/microsoft-authentication-library-for-js/tree/v3-lts/samples/msal-angular-v3-samples/angular-standalone-sample)
-- [Angular 17 Standalone Sample](https://github.com/AzureAD/microsoft-authentication-library-for-js/tree/v3-lts/samples/msal-angular-v3-samples/angular17-standalone-sample)
-- [Angular 18 Standalone Sample](https://github.com/AzureAD/microsoft-authentication-library-for-js/tree/v3-lts/samples/msal-angular-v3-samples/angular18-standalone-sample)
-The samples demonstrates basic configuration and usage, and may be improved and added to incrementally.
-See [here](https://github.com/AzureAD/microsoft-authentication-library-for-js/blob/v3-lts/samples/msal-angular-v3-samples/README.md) for a list of the MSAL Angular v3 samples and the features demonstrated.

package/docs/v3-v4-upgrade-guide.md DELETED Viewed

@@ -1,36 +0,0 @@
-# Upgrading from MSAL Angular v3 to v4
-MSAL Angular v4 includes security updates from MSAL Browser and adds Angular 19 support to the existing Angular 15-18 support.
-Please see the [MSAL Browser v3 migration guide](https://github.com/AzureAD/microsoft-authentication-library-for-js/blob/dev/lib/msal-browser/docs/v3-migration.md) for browser support and other key changes.
-## Changes in `@azure/msal-angular@4`
-### Using local storage
-Due to changes in MSAL Browser related to local storage encryption, please ensure you are checking that initialization has completed and that interaction status is None before calling any account APIs.
-```js
-this.msalBroadcastService.inProgress$
-    .pipe(
-        filter(
-            (status: InteractionStatus) => status === InteractionStatus.None
-        ),
-        takeUntil(this._destroying$)
-    )
-    .subscribe(() => {
-        this.loginDisplay = this.authService.instance.getAllAccounts().length > 0;
-    });
-```
-## Samples
-The following developer samples are now available:
-- [Angular B2C Sample](https://github.com/AzureAD/microsoft-authentication-library-for-js/tree/dev/samples/msal-angular-samples/angular-b2c-sample)
-- [Angular Modules Sample](https://github.com/AzureAD/microsoft-authentication-library-for-js/tree/dev/samples/msal-angular-samples/angular-modules-sample)
-- [Angular Standalone Sample](https://github.com/AzureAD/microsoft-authentication-library-for-js/tree/dev/samples/msal-angular-samples/angular-standalone-sample)
-The samples demonstrates basic configuration and usage, and may be improved and added to incrementally.
-See [here](hhttps://github.com/AzureAD/microsoft-authentication-library-for-js/tree/dev/samples/msal-angular-samples) for a list of the current MSAL Angular samples and the features demonstrated.

package/karma.conf.js DELETED Viewed

@@ -1,44 +0,0 @@
-/*
- * Copyright (c) Microsoft Corporation. All rights reserved.
- * Licensed under the MIT License.
- */
-module.exports = function (config) {
-    config.set({
-        basePath: "",
-        frameworks: ["jasmine", "@angular-devkit/build-angular"],
-        plugins: [
-            require("karma-jasmine"),
-            require("karma-chrome-launcher"),
-            require("karma-jasmine-html-reporter"),
-            require("karma-coverage-istanbul-reporter"),
-            require("@angular-devkit/build-angular/plugins/karma")
-        ],
-        client: {
-            jasmine: {
-                failSpecWithNoExpectations: true
-            },
-            clearContext: false, // leave Jasmine Spec Runner output visible in browser
-            captureConsole: true // turns on console logging for test debugging
-        },
-        coverageIstanbulReporter: {
-            dir: require("path").join(__dirname, "./coverage"),
-            reports: ["html", "lcovonly", "text-summary"],
-            "report-config":{
-                lcovonly: {
-                    projectRoot: "../.."
-                }
-            },
-            fixWebpackSourcePaths: true
-        },
-        reporters: ["progress", "kjhtml", "coverage-istanbul"],
-        port: 9876,
-        colors: true,
-        logLevel: config.LOG_INFO,
-        autoWatch: true,
-        browsers: ["ChromeHeadless"],
-        singleRun: true,
-        restartOnFileChange: true,
-        concurrency: 1
-    });
-};

package/ng-package.json DELETED Viewed

@@ -1,7 +0,0 @@
-{
-  "$schema": "./node_modules/ng-packagr/ng-package.schema.json",
-  "dest": "./dist",
-  "lib": {
-    "entryFile": "src/public-api.ts"
-  }
-}