All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.
- Added new FDI version support: 3.1, 4.0
- Removed redundant calls to
removeToken
- Fixed the session refresh loop in all the request interceptors that occurred when an API returned a 401 response despite a valid session. Interceptors now attempt to refresh the session a maximum of ten times before throwing an error. The retry limit is configurable via the
maxRetryAttemptsForSessionRefresh
option.
- Readds FDI 2.0 and 3.0 support
- Adds FDI 2.0 and 3.0 support
The shouldDoInterceptionBasedOnUrl
function now returns true:
- If
sessionTokenBackendDomain
is a valid subdomain of the URL's domain. This aligns with the behavior of browsers when sending cookies to subdomains. - Even if the ports of the URL you are querying are different compared to the
apiDomain
's port ot thesessionTokenBackendDomain
port (as long as the hostname is the same, or a subdomain of thesessionTokenBackendDomain
): supertokens/supertokens-website#217
- New FDI version support: 1.19
- Update test server to work with new node server versions
- Adds 1.18 to the list of supported FDI versions
- Fixes an issue where session tokens from network responses would not be consumed if they were not in lowercase (Credit: mattanimation)
- Adds Swift Package Manager support (Credit: mattanimation)
- Updates supported FDI versions to include
- Fixed an issue where the Authorization header was getting removed unnecessarily
- Refactors session logic to delete access token and refresh token if the front token is removed. This helps with proxies that strip headers with empty values which would result in the access token and refresh token to persist after signout
- Adds tests based on changes in the session management logic in the backend SDKs and SuperTokens core
- The SDK now only supports FDI version 1.16
- The backend SDK should be updated to a version supporting the header-based sessions!
- supertokens-node: >= 13.0.0
- supertokens-python: >= 0.12.0
- supertokens-golang: >= 0.10.0
- Properties passed when calling SuperTokens.init have been renamed:
cookieDomain
->sessionTokenBackendDomain
- The SDK now supports managing sessions via headers (using
Authorization
bearer tokens) instead of cookies - A new property has been added when calling SuperTokens.init:
tokenTransferMethod
. This can be used to configure whether the SDK should use cookies or headers for session management (header
by default). Refer to https://supertokens.com/docs/thirdpartyemailpassword/common-customizations/sessions/token-transfer-method for more information
- Fixes an issue with documentation generation
- Added documentation generation
- Adds support for using SuperTokens across app extensions (using App Groups)
- Inial Release