This log was last generated on Tue, 12 Jan 2021 00:51:26 GMT and should not be manually modified.
Tue, 12 Jan 2021 00:51:26 GMT
- Make scopes optional for msal-guard config (#2829) (joarroyo@microsoft.com)
- Interceptor, guard, and samples to use active account (#2784) (joarroyo@microsoft.com)
- Msal guard supports angular routes for login failure (#2803) (joarroyo@microsoft.com)
- Add additional interfaces to msal-guard (#2759) (joarroyo@microsoft.com)
Mon, 07 Dec 2020 23:02:52 GMT
- MSAL Angular v2 alpha.1 changes (janutter@microsoft.com)
Thu, 12 Nov 2020 00:45:30 GMT
- Add msal-angular-v2-alpha-0 (#2463) (joarroyo@microsoft.com)
Wed, 11 Nov 2020 23:33:20 GMT
- Pass generic to ModuleWithProviders for MsalModule v1, set supported Angular versions to 6-9 (#2577) (janutter@microsoft.com)
Tue, 25 Aug 2020 00:40:45 GMT
- Update protectedResources with wildcard, remove unprotectedResources from msal-angular (#2029) (joarroyo@microsoft.com)
Stable release of MSAL Angular v1. See beta versions below for complete list of changes.
- Requires
msal@1.3.0. - Requires
rxjs@6. - Adds support for Angular 6, 7, 8, 9.
- Drops support for Angular 4, 5.
MsalModule.forRootnow takes two arguement.- The first argument is the configuration object, which is the same
Configurationobject you would pass tomsal. - The second argument is a
MsalAngularConfigurationobject, containing the values forconsentScopes,popUp, andextraQueryParameters. - See the updated sample for an example of how to pass these configuration objects.
- The first argument is the configuration object, which is the same
- The
acquireTokenandloginmethods now take a singleAuthenticationParametersobject as parameters. getUser()is nowgetAccount().- Broadcast events now emit objects, instead of just strings.
- Applications using
Redirectmethods can optionally implement thehandleRedirectCallbackmethod (and have it run on every page load), which will capture the result of redirect operations. See the Angular sample for an example of how to implement. - Add
ssoSilentAPI. This API requires either aloginHintorsid, and is intended to be used when you want to SSO to an existing AAD session. Emitsmsal:ssoSuccessandmsal:ssoFailureevents.
- Ensure interceptor uses ID token property if response is of type id_token (#1528)
- Requires
msal@1.3.0-beta.0. - When MSAL Guard fails to silent SSO, prompt for interaction. (#1455)
- MSAL Guard should properly support hash routing and non-root base urls. (#1452)
- Fix isEmpty check for unprotectedResources. (#1454)
- Update handleRedirectCallback in Angular samples to log entire response. (#1428)
- Don't broadcast
msal:loginevents from MSAL Guard. (#1435) - Add guide for Configuration.
- Requires
msal@1.2.2-beta.2, which addredirectStartUrltoAuthenticationParameters, so that when a redirect operation from MSAL Guard is succesfully completed, redirect to the desired destination page. (#1343) - Short-circuit MSAL Guard if it detects it is loaded in an iframe, to prevent timeouts that occur as a result of redirecting. (#1337)
- If framework.protectedResourceMap/unprotectedResources is empty, use msalAngularConfig.protectedResourceMap/unprotectedResources. (#1355)
Fixes issues related to support for Angular 9 and Ivy.
- Library is now built using the Angular 9 CLI and
ng-packagr. (#1323) - Angular 9 sample now available in the samples folder. (#1312)
MSAL_CONFIGandMSAL_CONFIG_ANGULARavailable from the package's main export. (#1323)- Removes the
WindowWrapperclass. (#1323)
Fixes two issues related to aot mode.
- Requires
msal@1.2.2-beta.0, which addssetLoggerfunction to dynamically set the logger callback when running inaotmode. (#1213). - Moves
protectedResourceMapandunprotectedResourcesto MSAL Angular-specific configuration object.protectedResourceMapcan now be[string, string[]][]or aMap. This is also to mitigate issues withaotmode. (#1213).
Initial upgrade to be compatible with new version of Angular (6+).
- Requires
msal@1.2.1,rxjs@6,@angular/core@>=6,@angular/common@>=6as peer dependencies. rxjs-compatis no longer required by MSAL Angular.
aotcompiling will throw errors fornew Logger()andnew Map()("Function calls are not supported in decorators but 'Logger/Map' was called."). This will be addressed in a follow up release.
- Requires
msal@1.2.0-beta.1, which includes fixes for bugs with redirect methods. handleRedirectCallbackwill now emit events after returning from the redirect.
Initial upgrade to use msal@1.2.0.
msal@1.2.0package is now a peer dependency, and must be installed alongside@azure/msal-angular:npm install msal@1.2.0 @azure/msal-angular@alphaMsalModule.forRootnow takes two arguement.- The first argument is the configuration object, which is the same
Configurationobject you would pass tomsal. - The second argument is a
MsalAngularConfigurationobject, containing the values forconsentScopes,popUp, andextraQueryParameters. - See the updated sample for an example of how to pass these configuration objects.
- The first argument is the configuration object, which is the same
- The
acquireTokenandloginmethods now take a singleAuthenticationParametersobject as parameters. getUser()is nowgetAccount().- Broadcast events now emit objects, instead of just strings.
- Applications using
Redirectmethods must implement thehandleRedirectCallbackmethod (and have it run on every page load), which will capture the result of redirect operations. See the Angular sample for an example of how to implement.
- Fix msal-angular to transpile for IE11 compatibility: AzureAD#868
- Upgrade to msal-core version 0.2.2, namely including support for
storeAuthStateInCookiefor IE11.
- Fix msal-angular exports to properly support IE11: AzureAD#785
- Note: Unfortunately, the fix above caused breakage with
aotcompiling, so0.1.3has been deprecated in npm. We recommend pinning to0.1.2while we work on a fix. See AzureAD#798
- Note: Unfortunately, the fix above caused breakage with
-
AOT fix for protectedResourceMap issue AzureAD#407
-
Broadcast message returns object
-
Fixed AOT issue AzureAD#386
-
Upgraded to latest msal-core version 0.2.1
Preview Release