Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Access Token Exposure Control
This PR introduces a security enhancement for controlling access token exposure in browser-based applications, following the OAuth best practices.
Changes
enableAccessTokenEndpoint
to theAuth0ClientOptions
interface. This boolean flag controls whether the/auth/access-token
endpoint is accessible from client applicationsfalse
, it prevents direct exposure of access tokens to browser-based applications, enhancing securitytrue
for backward compatibilityReferences
Testing
PASSING
How to Test
enableAccessTokenEndpoint: false
in your Auth0 client configuration/auth/access-token
from client code fail appropriatelyMigration Guide
For applications that need to improve security by adopting the Token Mediating Backend pattern:
Update your Auth0 client configuration:
Replace client-side API calls using tokens with server-side endpoints:
Update any client-side code that depends on direct token access to use server-side proxies instead