v5.0.0
5.0.0 (2024-10-28)
⚠ BREAKING CHANGES
- Authorization: AuthorizationManager uses in-memory storage by default.
Features
- Authorization: AuthorizationManager uses in-memory storage by default. (09f6839)
An in-memory storage mechanism is used by the AuthorizationManager by default moving the implementation to "secure by default". Based on the impact to downstream applications and UX, we are considering this a breaking change.
To use a different storage mechanism, a well-known storage system (i.e., localStorage, sessionStorage) can be provided as the storage configuration option on creation.
authorization.create({
// ...
storage: localStorage
});To use a custom storage mechanism, any Storage implementation can be provided.
class MyCustomStorage implements Storage {};
authorization.create({
// ...
storage: new MyCustomStorage();
});