Allow Custom Token Length in Sanctum Token Generation #553
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.
This update allows the token length in
generateTokenString
to be configurable via thesanctum.entropy_length
config variable. It defaults to 40 for backward compatibility while enabling developers to define custom lengths for enhanced security.Custom lengths provide users the flexibility to enhance token security or align with their application's unique requirements, such as stricter compliance standards or integration needs.
The change is fully backwards-compatible and simplifies token customization for varied application needs. All tests passed.