-
Notifications
You must be signed in to change notification settings - Fork 206
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[fxa-event-broker] Guardian webhook is not being called. #3324
Comments
Do you know the guardian users fxa uid? What's an easy way to create a guardian user that we can reproduce with? |
Sure, you can test/delete whatever these:
Let me know if you need more to play with. Thanks! |
Ah, I misconfigured things, I needed to add authentication, which is done now |
@jbuck woot. prod next? |
This has been done on prod now |
Description
We've (@bbangert, @jrgm) done a few manual test calls to the webhook that came through and the signature was verified properly, etc. Those test calls are the only calls that appear in our logs.
Steps to reproduce
Delete a guardian user on stage.
Expected result
The webhook on guardian stage is called with the correct info.
Actual result
The webhook on guardian stage isn't called.
Environment
Stage.
┆Issue is synchronized with this Jira Task
┆Issue Number: FXA-532
The text was updated successfully, but these errors were encountered: