LinkinStars commented on issue #1220: URL: https://github.com/apache/answer/issues/1220#issuecomment-2763048168
> Specifically, when logging in with oauth provider getting presented with: > >  > > Is there a way to avoid this w/o having `email_verified=true` on oauth response? > > Update, looking at https://github.com/apache/answer-plugins/blob/main/connector-basic/basic.go it appears there isn't but seems like it would be a good option to offer for clients who's OAuth emails are implicitly verified. Would it be acceptable to offer such an option? I can draft up a PR quickly if so. @shockdm Let me clarify. There are three configurations 1. User Email JSON Path: Path in the OAuth2 User JSON to the user email. eg: user.email 2. Check Email Verified: If set to true, the email will be verified by email_verified_json_path. If not, the email is always believed to have been verified. 3. Email Verified JSON Path: Path in the OAuth2 User JSON to the email verified. eg: user.email_verified If the `Check Email Verified` option is set to true, it will verify the email. If it is set to false, it will not verify the email. That is, if `Check Email Verified` is set to false, as long as the third party provides the email address in the json according to the `User Email JSON Path`, there is no need to verify. If there is a validation, such as your screenshot, it is obvious that the email is not provided. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
