We are using ThirdPartyEmailPassword and Email Ver...
# support-questions-legacyp
phoenix1413.
09/23/2023, 6:10 AMWe are using ThirdPartyEmailPassword and Email Verification recipes together. We need Email Verification only for Email Password users and not for social users. But When we Try to use "@verifySession" annotation in the backend in case of social login. It is considering it as invalid session. and giving an error like this : {
"message": "invalid claim",
"claimValidationErrors": [
{
"id": "st-ev",
"reason": {
"message": "wrong value",
"expectedValue": true,
"actualValue": false
}
}
]
}
Can anyone please let us know what to do in this case?
r
rp_st
09/23/2023, 6:28 AMHey @phoenix1413.
rp_st
09/23/2023, 6:28 AMThis social login provider doesnt give the email verification status?
p
phoenix1413.
09/23/2023, 6:29 AMNo @rp_st they are staying as not email verified somehow
r
rp_st
09/23/2023, 6:30 AMRight. So wouldn’t you want to verify the user’s email in that case?
n
namanchhabra_60978
09/23/2023, 6:39 AM@rp_st he is unable to send the verification email also, for unverified sso users
namanchhabra_60978
09/23/2023, 6:40 AMgetting a 404 error in that too
r
rp_st
09/23/2023, 6:40 AMWhich api gives 404?
p
phoenix1413.
09/23/2023, 7:02 AMNo @rp_st
phoenix1413.
09/23/2023, 7:02 AMThey are logging in from social accounts which are already legit so we don't need to verify them.
phoenix1413.
09/23/2023, 7:02 AMAnd we just found out it's automatically verifying for Google accounts but not verifying for azure ad accounts
phoenix1413.
09/23/2023, 7:02 AMIt's not 404, it's 405 method not allowed
r
rp_st
09/23/2023, 7:03 AMYou can override the azure provider’s getUserInfo function to set email verified to true. This way, it will behave like google login
p
phoenix1413.
09/23/2023, 7:04 AMOk @rp_st , we'll try that. Thank you so much 😊
phoenix1413.
09/23/2023, 7:30 AM@rp_st , what might be the reason that verification emails are not being sent if the user logged in with social accounts. And from super tokens dashboard also, we're unable to make the user verified. When we try to make them verify from the dashboard, dashboard is throwing an error
r
rp_st
09/23/2023, 7:31 AMis there any backend error stack? It may be a bug
rp_st
09/23/2023, 7:31 AMand what is the network request status code?
p
phoenix1413.
09/23/2023, 7:31 AM405 method not allowed
r
rp_st
09/23/2023, 7:31 AMcan you show me the network tab?
p
phoenix1413.
09/23/2023, 7:32 AMSure
phoenix1413.
09/23/2023, 7:33 AMr
rp_st
09/23/2023, 7:34 AMcan you enable backend debug logs of supertokens when this API is called?
rp_st
09/23/2023, 7:34 AMand show me the output
p
phoenix1413.
09/23/2023, 7:34 AMsure
phoenix1413.
09/23/2023, 7:37 AMr
rp_st
09/23/2023, 7:38 AMthese aren't supertokens logs. Can you enable those and show me the output?
rp_st
09/23/2023, 7:38 AMsee the debugging section in our docs
p
phoenix1413.
09/23/2023, 7:39 AMok @rp_st . Will provide it.
4 Views