This guide includes all the information you need to update auth0.js from v8 to v9. Find out if you should upgrade or not by reading Migrating to Auth0.js v9.
Angular 1.x applications usually use the angular-auth0 packagewhen authenticating with Auth0. To use auth0.js v9 you need to update to the latest version (3.x).
You can update the angular-auth0 library using npm or yarn.
# installation with npm npm install --save angular-auth0 # installation with yarn yarn add angular-auth0
The script files need to be added to your build system, or added to the project with a script tag.
Update the Auth0.js library using npm or yarn.
# installation with npm npm install --save auth0-js # installation with yarn yarn add auth0-js
Once updated, you can add it to your build system or bring it in to your project with a script tag.
If you do not want to use a package manager, you can retrieve Auth0.js from Auth0's CDN.
Configure your Auth0 application for embedded login
When implementing embedded login, Auth0.js v9 will use cross-origin calls inside hidden iframes to perform authentication. To make sure this can be done securely, Auth0 needs to know the domains where you will be hosting your applications.
Add the domain to the Allowed Web Origins field. You can find this field in the Application Settings area of your Dashboard.
Change calls to getProfile()
getProfile() function was reimplemented in Lock 11. The previous implementation received an ID Token as a parameter and returned the user profile.
The new implementation requires an Access Token parameter instead.
Review calls to getSSOData()
getSSOData() function was reimplemented in Auth0.js v9 to simplify migration from older versions, but the behavior is not exactly the same.
The function will not work as expected when you use it in Web Applications that use the Authorization Code Flow (such as when you specify
response_type='code'). It will always return that there is not a current session.
If you want to avoid showing the Lock dialog when there is an existing session in the server, you can use the checkSession() function in Auth0.js.
We recommend that you do not use
getSSOData() and use checkSession() instead. Note that in order for
checkSession() to work properly, it requires that you set the Allowed Web Origins field in the dashboard.
If you are going to keep using
getSSOData(), take into account the changes in the return values described in the table below. In most applications, the only value that was actually used was the
sso property, which still has the same semantics.
|Property||Old Value||New Value|
|sessionClients||List of applications ids the user has active sessions with||List with a single element with the client id configured in auth0.js|
|lastUsedClientId||The client id for the last active connection||The last application used when authenticating from the current browsers|
|lastUsedUserId||The user id for the current session||The same|
|lastUsedUsername||User's email or name||The same (requires
|lastUsedConnection||Last used connection and strategy.||Last connection used when authenticated from the current browser. It will be
In order for the function to work properly, you need to ask for
scope='openid profile email' when you initialize Auth0.js.
Auth0.js v9 will default the value of the scope parameter to
openid profile email.
If you are running your website from
http://127.0.0.1 and you do not specify the
openid profile email scope when initializing auth0.js, calling the
getSSOData() method will result in the following error in the browser console:
Consent required. When using `getSSOData`, the user has to be authenticated with the following scope: `openid profile email`
This will not happen when you run your application in production, or if you specify the required scope. You can read more about this scenario in the documentation on skipping consent for first-party applications.