This is behavior I would not expect, so I'm filing this issue.
If you set up a transactional webhook listening for the login success event and return a 500, it fails a login of authenticationTypePASSWORD but not if the login event happens via SSO (authenticationType of PING).
To replicate:
stand up a webhook receiver (php code below for ease of use, just run it with php -S 0.0.0.0:8000
associate it with the login success event in webhooks tab
enable it on the tenant with a transaction level of 'all webhooks must succeed'
What happened?
This is behavior I would not expect, so I'm filing this issue.
If you set up a transactional webhook listening for the login success event and return a 500, it fails a login of
authenticationType
PASSWORD
but not if the login event happens via SSO (authenticationType
ofPING
).To replicate:
php -S 0.0.0.0:8000
You'll succeed. If you look at the network tab, you can see that the
authorize
path from FusionAuth is called.I'd expect it to fail because a non 2xx status code is returned.
Version
1.51.1
Affects Versions
No response