swift-island-66287
05/21/2023, 7:23 AM00000000-0000-0000-0000-000000000000
When I create an account using a password, I get a proper ID back. I use this ID in another DB to link to this user. Did I miss something while setting up google OIDC?swift-island-66287
05/21/2023, 7:47 AMsub
provided by google when it is in test mode?swift-island-66287
05/21/2023, 8:41 AMwide-dawn-74672
05/21/2023, 8:43 AMwide-dawn-74672
05/21/2023, 8:44 AMswift-island-66287
05/21/2023, 8:45 AMwide-dawn-74672
05/21/2023, 8:46 AMswift-island-66287
05/21/2023, 8:47 AMswift-island-66287
05/21/2023, 8:47 AMwide-dawn-74672
05/21/2023, 8:57 AMswift-island-66287
05/21/2023, 8:58 AMswift-island-66287
05/24/2023, 6:00 AMcan_interrupt
for now, but with this, the user will be created even if the hook fail, which is not optimal.swift-island-66287
05/24/2023, 6:01 AMdazzling-napkin-4938
05/24/2023, 8:20 AM{
identity: {
public_metadata: {
memberId: WHATEVER
}
}
which gets written to kratos. The second webhook then has the kratos identity ID and we update our database with that.
I’m not sure it’s possible to do it another way - one of the webhooks is called before the identity is written to the database, and so the ID does not exist yetswift-island-66287
05/24/2023, 8:21 AMdazzling-napkin-4938
05/24/2023, 8:23 AM