29 lines
1.0 KiB
Markdown
29 lines
1.0 KiB
Markdown
|
# Configure Webhook Notifications
|
||
|
|
|
||
|
|
**ID:** DEV-003
|
||
|
|
**Priority:** Medium
|
||
|
|
**Status:** Planned
|
||
|
|
|
||
|
|
## User Story
|
||
|
|
As a developer, I want to configure webhooks so that my application is notified in real-time when authentication events occur.
|
||
|
|
|
||
|
|
## Acceptance Criteria
|
||
|
|
- [ ] Register webhook endpoints with URL and secret
|
||
|
|
- [ ] Select which events to subscribe to
|
||
|
|
- [ ] Events include: user.created, user.login, user.logout, org.member.added, etc.
|
||
|
|
- [ ] Webhook payloads include event type, timestamp, and relevant data
|
||
|
|
- [ ] Signature verification using shared secret (HMAC)
|
||
|
|
- [ ] Retry logic for failed deliveries (exponential backoff)
|
||
|
|
- [ ] Webhook delivery logs with success/failure status
|
||
|
|
- [ ] Test webhook button to send sample event
|
||
|
|
|
||
|
|
## Technical Notes
|
||
|
|
- Create Webhook model with URL, secret, events, and status
|
||
|
|
- Queue webhook deliveries for reliability (consider bull/bullmq)
|
||
|
|
- Sign payloads with HMAC-SHA256
|
||
|
|
- Timeout for webhook delivery (10 seconds)
|
||
|
|
- Dashboard for delivery monitoring and debugging
|
||
|
|
|
||
|
|
## Related TODOs
|
||
|
|
- New feature - event-driven integration
|