1 Answer
- Newest
- Most votes
- Most comments
1
Hi,
SUB is not available in pre-signup trigger because the user hasn't been created at this stage (it is "pre" sign-up, meant for validation to decide whether to allow the sign-up to continue or reject the request). If you want to propagate the SUB to backend you should use PostConfirmation trigger for this, this will be triggered after the user has been created and confirmed.
Relevant content
- Accepted Answerasked 9 months ago
- asked 5 years ago
- asked a year ago
- asked a year ago
AWS OFFICIALUpdated a year ago- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 10 months ago
Thanks for the quick reply.
Does post confirmation trigger execute before the authentication flow is complete? We need the user to be present in the database before user is redirected back to the frontend after the sign up?
I did some experimentation and post confirmation is indeed part of the external provider sign up flow. That solves the issue, thanks! The documentation could be more clear on this though.
Noted also that when using adminCreateUser, the post confirmation doesn't trigger. I can imagine there would be many use cases for using a trigger which runs every time after the user has been created to the pool, no matter which way the creation happened.