Hello, I have a question I can't solve, when I cre...
# talk-kratos
p
Hello, I have a question I can't solve, when I create an account and then I do the verification, it says this, then I click on "Go Back" it says "You successfully verified your email address." but I have to relogin because the callback doesn't work.
s
Do you get this error after putting a valid verification code?
p
Yes
And it's working the account is actually verified but no automatic callback
@steep-lamp-91158 Let me know if you have any idea
s
I'm looking into it, and it looks a bit weird 😅 let me dig a bit more
but I can definitely reproduce
OK I traced it down to the fact that you are using OAuth2 wrapped Ory Identities. There seems to be a bug with the after-registration verification hook, because it wrongly expects that a user already has a valid session with the OAuth2 provider.
We'll work on a fix
Do you require verified addresses?
Just to make sure, previously a user would need to first verify and then log in again right? The only change is that now this error appears in the middle, but it still works as it should except for the error
p
"Do you require verified addresses?" Yes need to be sure they verify the email before login
"Just to make sure, previously a user would need to first verify and then log in again right? The only change is that now this error appears in the middle, but it still works as it should except for the error"
Ideally, once it's been verified, a callback is sent directly and it's logged in. If not, simply verifying yes is already good enough.
s
OK, we have a fix prepared but it will not land on production before beginning of next week. A workaround would be to enable sessions after registration, and then block certain actions for non-verified users in your application logic.
Is there a specific reason you went for the OAuth2 approach?
p
"Is there a specific reason you went for the OAuth2 approach?" i migrate from auth0 to your solutions, 2 day ago and it's how my app works
"OK, we have a fix prepared but it will not land on production before beginning of next week. A workaround would be to enable sessions after registration, and then block certain actions for non-verified users in your application logic. (modifié)" thanks
"Ideally, once it's been verified, a callback is sent directly and it's logged in. If not, simply verifying yes is already good enough." for the call back any fix ?
s
the fix should also allow to issue a session after successful verification, I'll ping you on the details once available
p
They it's in production please ? (we are receving o lot of message from users about this)
@steep-lamp-91158 I've retested the bug and do you have any idea when the patch will be in production?
s
There was a bug in the fix that we caught on staging, but looks good now. We want to release it tomorrow
The release pipeline is now triggered, so it should be live in a few minutes, I'll keep you posted
all resolved now, I just did the flow on your site and was successfully logged in after completing verification
thanks for your patience
just fyi, it seems that I did not get 5 credits on signup, let me check that
are you using webhooks for that?
ok I did get them now that I logged in again in an incognito tab