fix: set additional scopes and make email_verified optional #63
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.
FusionAuth 1.50.0 introduced the Scope Handling Policy. In new installation it's set to
scopeHandlingPolicy.Strict
, which causes previously available fields to not be included in the response.The fusionauth_config.json was updated to include the additional scopes
email
andprofile
.In the
UserInfo
class, the required fieldemail_verified
was made optional, providing a null default value to prevent issues when this field is not provided.Closes #62