AAI-166 registration endpoint for Galaxy#11
Merged
Conversation
amandazhuyilan
previously approved these changes
May 14, 2025
amandazhuyilan
left a comment
Contributor
There was a problem hiding this comment.
Not sure if its ready for review yet but so far so good
amandazhuyilan
approved these changes
May 15, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
AAI-166: endpoint in the backend that accepts data from our frontend registration form, and makes a request to the Auth0 management API to create/register a new user.
It seems like we probably want some basic protection around this API, so have added basic JWT verification so we don't just get spammed with register requests from bots.
Changes
Checklist
How to Test Manually (if necessary)
Run
uv run pytest