Releases: AzureAD/microsoft-authentication-library-for-js
Releases · AzureAD/microsoft-authentication-library-for-js
Release msal v1.0.1
Updates:
- Fixed bug where navigateToLoginRequestURL = false would cause callback to not fire (#696)
- Fixed bug where null request object would cause null pointer exception for state parameter (#698)
- All msal related cache items are deleted on logout (#709)
- Fixed bug where "user cancelled" error in acquireTokenPopup would not throw (#707)
- Logout endpoint now uses the given EndSessionEndpoint from the oauth discovery endpoint response (#716)
- Now uses base64.js instead of window.atob (#712)
- Fixed bug where login_hint was added if sid was already populated. (#700)
Release msal v1.0.0-preview.5
Updates:
- Error First Callbacks PR #658
- Claims Request Support PR #664
- loginInProgress() as a public function #671
- 'state' moved from config to request, returning the user state if passed stripping the GUID #674 #679 #681
- cache cleanup of all values (keys cleanup will be done in next release) #675
- made loading iFrame timeout in silent calls configurable, 'navigateFrameWait' #676
- readme updated with latest code patterns #672
Release msal v1.0.0
- Formal release of msal-1.0.0 which includes all the msal-1.0.0-preview.x changes.
- Includes breaking API Changes - please find the details @https://github.com/AzureAD/microsoft-authentication-library-for-js/wiki/MSAL.js-1.0.0-api-release
Release msal v1.0.0-preview.4
Release Notes
- Add dist back into npm package as a valid build artifact
Release msal v1.0.0-preview.3
Add a hook in package.json to build msal js before npm publish to have the libraries up to date
Release msal v1.0.0-preview.2
Release msal v1.0.0-preview.1
Included in release
- Fix dependencies for Tslib
Release msal v1.0.0-preview.0
1.0.0-preview.0
New Features (Breaking Changes)
As announced earlier @https://github.com/AzureAD/microsoft-authentication-library-for-js/wiki/MSAL.js-1.0.0-preview-changes we are excited to announce the preview release.
Release notes:
Configuration Object
- Initialization of the MSAL JS library – We introduced a ‘Configuration’ object that can be sent through the constructor of UserAgentApplication() class.
Request Object
- ‘Request’ object is introduced for all login/accessToken calls, this replaces previous overloading of login/acquireToken calls
- Users can choose to pass optional parameters to finetune their requests for authentication and authorization.
- 'User' object is now replaced with 'Account' => the public API getUser() is now getAccount() with more enhanced data.
Response and Error Objects
- ‘Response’ and 'Error' objects are introduced for server responses and app failures
- For ‘Redirect’ usecases, explicit success and failure call backs should be passed to ‘handleRedirectCallbacks()’.
- For 'Popup' and 'Silent' usecases, a promise pattern i.e.,' .then and .catch' can be used.
- Note: Error objects are better classified and messaged with this release. Detailed documentation for Error Handling will be added soon in docs
The 'Configuration', 'Request', 'Response' and 'Error' datatypes and their usage is detailed in the changelog.md @https://github.com/AzureAD/microsoft-authentication-library-for-js/blob/dev/lib/msal-core/changelog.md
We will follow up with a detailed blog post and a Quickstart Application soon with these changes.
Release msal v0.2.4
- Features
- Removal of prompt-select account
- Removes prompt parameter from interactive login and acquireToken requests, which include:
- loginRedirect
- loginPopup
- acquireTokenRedirect
- acquireTokenPopup
- acquireTokenSilent will continue to pass prompt=none
- When no prompt parameter is passed, the server:
- Attempts SSO. If there is a single available session, SSO will succeed.
- This session can come from cookies or the OS, and must match other request parameters such as login_hint, domain_hint, etc.
- If SSO fails, then you see either a login prompt or account selector
- If there are no active sessions, the user will see a login prompt
- If there are one or more active sessions but SSO was unable to match to a session with correlating request parameters, the user will see an accountSelector
- Attempts SSO. If there is a single available session, SSO will succeed.
- Clients can set the prompt value to any of the allowed values with extraQueryParameters. Please read docs here for more information: https://github.com/AzureAD/microsoft-authentication-library-for-js/wiki/Prompt-behavior
- Removes prompt parameter from interactive login and acquireToken requests, which include:
- Unified Cache
- To support migration from ADAL.js to MSAL.js.
If your app is currently using ADAL.js and the user already has an existing session, this release supports SSO without requiring login in MSAL.js during the migration.
More details on how to achieve this are available here: https://github.com/AzureAD/microsoft-authentication-library-for-js/wiki/Sso#sso-when-updating-from-adaljs-to-msaljs - A sample is available in the repo in samples/UnifiedCacheTestApp
- To support migration from ADAL.js to MSAL.js.
- Redirect URI as a function
- Set default redirectUri/postLogoutRedirectUri to a function returning
the current location.href, instead of the location.href from when the
UserAgentApplication was instantiated. Enables use of history.pushState.
One test updated, and tests added for redirectUri/postLogoutRedirectUri
as functions.
#462 - Fixes #458
- Set default redirectUri/postLogoutRedirectUri to a function returning
- Unit and End to end testing for msal-core enhanced
- Removal of prompt-select account
- Bug Fixes
- Package updates:
- added ajv 6.6.1
- added fork-ts-checker-webpack-plugin: "^0.5.1"
- jasmine-node: ^2.0.1 to ^1.16.2
- karma-webpack: ^2.0.5 to ^4.0.0-rc.5
- @types/jasmine-ajax:3.1.35 to 3.1.39
- jshint: 2.9.5 to 2.9.7
- webpack: 3.6.0 to 4.27.1
- changed from awesome-typescript-loader to ts-loader 5.3.1
- added webpack-cli: "^3.1.2",
- added webpack-dev-middleware: "^3.4.0"