Auth0 authentication for Single Page Applications (SPA) with PKCE
MIT License
Bot releases are hidden (Show)
Published by auth0-oss over 2 years ago
Added
Security
Published by auth0-oss over 2 years ago
Published by auth0-oss over 2 years ago
Fixed
Published by auth0-oss over 2 years ago
Added
Changed
Fixed
Security
Published by auth0-oss almost 3 years ago
Fixed
Security
Published by auth0-oss almost 3 years ago
Changed
Fixed
Published by auth0-oss about 3 years ago
This release fixes an anomoly with a new type we exposed in #803, where it was incorrectly wrapped with Partial
. We don't expect this change to introduce any issues, but if you are affected please raise it on our issue tracker.
Fixed
Published by auth0-oss about 3 years ago
Republished version 1.19.0
, which got published during a period npm was suffering downtime issues, resulting in 1.19.0
being released but not installable for end users. Users should install 1.19.1
instead.
Published by auth0-oss about 3 years ago
Added
Published by auth0-oss about 3 years ago
Added
Changed
Fixed
Published by auth0-oss about 3 years ago
Fixed
Published by frederikprijck about 3 years ago
Added
useFormData
to enable application/x-www-form-urlencoded
requests #768 (stevehobbsdev)Changed
domain
that includes http
or https
. #768 (stevehobbsdev)Published by stevehobbsdev over 3 years ago
This release fixes an edge case when using logout({ localOnly: true })
, where it generates a race condition if you happen to query for SDK state directly after logging out.
Now, logout
can return a Promise when using a custom cache implementation. In general, if you're interested in accurately assessing SDK state after logging out locally, you should await the result and act afterwards.
const logout = async () => {
await auth0.logout({ localOnly: true });
const authed = await isAuthenticated();
}
Fixed
This release adds a new extensible cache API, that enables you to bring your own cache implementation instead of relying on our built-in in-memory storage and localStorage
implementations.
It's a Promise-based API that opens up the possibility to provide a more secure and complex cache to the SDK.
Here's a simple example that shows how sessionStorage
support can be added to the cache:
const sessionStorageCache = {
get(key) {
return Promise.resolve(JSON.parse(sessionStorage.getItem(key)));
},
set(key, value) {
return Promise.resolve(sessionStorage.setItem(key, JSON.stringify(value)));
},
remove(key) {
sessionStorage.removeItem(key);
return Promise.resolve();
},
};
await createAuth0Client({
domain: '<AUTH0_DOMAIN>',
client_id: '<AUTH0_CLIENT_ID>',
redirect_uri: '<MY_CALLBACK_URL>',
cache: sessionStorageCache
});
You can read more about the cache API in the readme doc.
Added
Published by adamjmcgrath over 3 years ago
Published by stevehobbsdev over 3 years ago
Added
redirectMethod
option to loginWithRedirect
#717 (slaywell)Changed
Fixed
Published by stevehobbsdev almost 4 years ago
Changed
Fixed
Security
Published by frederikprijck almost 4 years ago
Changed
Fixed
Remarks
This release updates the getUser
return type to be more correct. Instead of returning Promise<TUser>
, it now returns Promise<TUser | undefined>
, which might lead to an Object is possible 'undefined'
compiler error in situation where the return value is not checked for being undefined while having set the TypeScript's --strictNullChecks
compiler flag to true
.
Published by frederikprijck almost 4 years ago
Added
Changed