https://www.ory.sh/ logo
Join Slack
Powered by
i think that it could work by setting `can_interru...
# ory-network
h
i think that it could work by setting 
can_interrupt
to false
e
if we set 
can_interrupt: false
and 
response.ignore: false
it fails to get the identity from /admin/identities/ with http 404 error but if we set 
can_interrupt: false
and 
response.ignore: true
flow continues and We get the webhook notification with userId in it and we are able to call admin endpoint the get user information.
I think, after registration web-hook with external service integration in a blocking scenario waits for the success response from external service before persisting the user. The external service in our case depends on persisted user. When the external service triggered by the web-hook with userId in the payload our services in turn calls 
admin/identities
endpoint to get the user data for the given 
userId
since it does not exist yet it fails and as a result registration flow fails. Could this be the reason ? In a Non blocking scenario(
can_interrupt: false
 and 
response.ignore: true
) we are able to get userdata from 
admin/identities
endpoint without an issue.
h
I have to check but think that 
can_interrupt
blocks the user creation on our end unless the web hook says “it is ok to save the user”. So if it is true, the user does not yet exist in the DB when the webhook is called
e
If you could clarify persistence behaviour please I would really appreciate it.
Hello hello, @high-optician-2097 Did you clarify the behaviour, we are kind of stuck here?
h
I replied on your private slack 🙂
e
Thank you very much 🙂
Open in Slack
PreviousNext
Powered by