I am trying to configure a custom social connection and have an email verification sent to the user. The connection does not have a built in mechanism for verifying emails so we do not want to trust what it provides us.
When we fetch the user profile, I am making sure to set the email_verified to false. Despite this, no email is being sent to the end user. When I look at the user that was created, I see that the email verification is pending but there is still no email to sent.
We are currently on the free plan and are using our own Mail Gun API key (which I have validated it works).
Additionally, I have played around with a variety of suggestions which use a rule + the user management API to. trigger an email job directly. This STILL does not seem to trigger an email.
Do we simply need to upgrade our plan to the essentials version? Is email validation even supported for Custom Social connections?
hello @anne165hernadez, I have updated to the essentials plan but am not seeing any resolution to the issue.
I have created a new application that dopes not use the rule based approach to trigger an email verification (from the docs it should just happen). Additionally I have verified the following:
- I am using a custom email provider and the
from is the same in both the template and the provider. I have also sent a test email and it appears to work fine
- I have made sure the email verification template is enabled
- I have created a new application and configured the Custom SSO connection
- I am mapping the user properties and setting
email_verified: false in the user profile mapper
Additionally, I enabled the user password database and logged in via that route and have confirmed that an email verification is sent using the custom email provider credentials when using that flow
I feel like there must be some configuration some-where that I am missing, however all of the docs say that it should simply happen