Hi team,
Following the recommendation from the ARC support team (https://arcpublishing.atlassian.net/servicedesk/customer/portal/2/ACS-38872), we opened a ticket to implement the following development: We have detected that when a user who is not verified in ARC logs in via a social connector (e.g., Google) or via SSO, the social connector or SSO is linked to the user, leaving the user logged in but not verified.
In our system, this causes an inconsistency because, since the user is not verified, the information is not communicated to our CDP, resulting in a discrepancy between the systems and causing a misalignment.
We need the user to be automatically verified whenever this situation occurs.
If you need more information from us, please let us know
Thanks
Best regards
Guest
Hello, thank you for submitting this idea on improving the social login verification flow. We are releasing an improvement this week that marks a user's email address as "verified" when they sign in with a social provider that returns the
email_verifiedflag. This includes Google and Apple, as well as custom OIDC providers when you includeemail_verifiedin the ID token.