[13.x] Use UUID to identify clients by default #1764
Merged
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.
Clients are now identified by UUID by default. According to RFC6749 the client identifier must be a unique string. It's also more secure than incremental integer IDs.
Changes
Passport::clientUuids()
method has been removed.Passport::setClientUuids()
method has been removed.'passport.client_uuids'
config property has been removed.Upgrade Guide
You may set
Passport::$clientUuids = false
onboot
method of your application'sApp\Providers\AppServiceProvider
class to identify clients by incremental integer IDs.