Skip to content
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

Set up DocuSign webhook handler for waivers #245

Merged
merged 2 commits into from
Jan 17, 2024
Merged

Conversation

samderanova
Copy link
Contributor

Resolves #218.

Changes

  • Create new POST route for /user/waiver
  • Write handler functions to parse DocuSign Connect webhook event
    • Validate HMAC signature of event payload
    • Update user status accordingly
  • Unit tests
  • Update README.md

Testing

We'll be assigning the staging domain for this deployment to allow testing with DocuSign's webhook.

  1. Log into the staging deployment.
  2. Notify me so I can grant you a status of ACCEPTED.
  3. Navigate to https://staging.irvinehacks.com/api/user/waiver to access the waiver.
  4. Complete the waiver.
  5. Notify me so I can check whether your status has changed to WAIVER_SIGNED.

To test other scenarios, you can not ask me to grant you the ACCEPTED status and attempt to access /user/waiver. You should still be able to access the waiver, but now we are assuming you are an external participant. In this case, continue completing the waiver and notify me so I can check again whether your status has changed to WAIVER_SIGNED.

Note: After merging #244, users will be able to see whether they have signed the waiver in the user portal.

Copy link
Contributor

github-actions bot commented Jan 16, 2024

Deploy preview for irvinehacks-site-2024 ready!

Name IrvineHacks 2024 Site
Preview Visit Preview
Commit 07d91e1

- Create new POST route for `/user/waiver`
- Write handler functions to parse DocuSign Connect webhook event
	- Validate HMAC signature of event payload
	- Update user status accordingly
- Unit tests
- Update README.md

Co-authored-by: Taesung Hwang <[email protected]>
@samderanova samderanova force-pushed the setup/docusign-webhook branch from 351eee0 to 800d55a Compare January 16, 2024 21:14
Copy link
Member

@taesungh taesungh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Tested on staging domain through new Portal design. Didn't receive a confirmation email from DocuSign, perhaps a limitation of their demo environment. Will test again once #246 is done.

@samderanova samderanova merged commit 3d5590d into main Jan 17, 2024
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[API] Set up DocuSign webhook
3 participants