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.
Latest version of Socialite (https://github.com/laravel/socialite/releases/tag/v5.12.0) added a breaking bug for EVE authentication with this PR : laravel/socialite#684
The fix is to change the list of fields sent in the form body to the token endpoint to no longer include client_id and client_secret because they are provided in the Authorization header. This is the "correct" way to provide client_id/client_secret to an OAuth endpoint (that was the point of the PR on socialite in the first place). So the fix I propose is to accept this behavior and only remove the unecessary fields from the form body.
The Original SeAT error was :
meaning the client_id/client_secret combo should be in the Authorization header OR the form body, but not both.