Bug: deauth callback requests broken?

Bugabee
1

Working on debugging an issue with TaskRatchet, and couldn’t figure out why taskratchet wasn’t honoring events sent to its deauth webhook. Used webhook.site to listen to the request sent from beeminder, and got this:

curl -X 'POST' 'https://webhook.site/d8e138e5-ee42-4d09-88e8-7852fa1d53fe' \
  -H 'content-type: application/x-www-form-urlencoded' \
  -H 'content-length: 13' \
  -H 'host: webhook.site' \
  -H 'user-agent: Ruby' \
  -H 'accept: */*' \
  -H 'accept-encoding: gzip;q=1.0,deflate;q=0.6,identity;q=0.3' \
  -d $'access_token='

It’s sending an empty access token, meaning taskratchet can’t link the event back to the user who revoked the app.

Can we get this fixed?

Thanks!

1 Like
2

Worked on this with @bee, and should be fixed now! Events sent to deauth webhooks now include username and access_token_hash.

1 Like