feat: implement authorization code flow with azul and data browser (#4793)#4796
Merged
feat: implement authorization code flow with azul and data browser (#4793)#4796
Conversation
based on poc patches in #4793. points anvil-cmg dev at hannes' personal azul deployment with his client id, matching the original poc; subsequent commit switches to the real anvildev endpoints. Co-authored-by: hannes-ucsc <hannes-ucsc@users.noreply.github.com> Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
revert data url to the real anvildev service, swap to the anvildev google client id, and wire the authorize field through the google provider so findable-ui's authorization code flow targets service.anvil.gi.ucsc.edu/user/authorize. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Contributor
There was a problem hiding this comment.
Pull request overview
Updates the AnVIL CMG dev site configuration to support Azul’s OAuth 2.0 authorization code flow by adjusting the Google OAuth provider configuration used by the Data Browser.
Changes:
- Update the Google OAuth
CLIENT_IDfor AnVIL CMG dev. - Add an
authorizeendpoint (/user/authorize) to the Google provider config for code flow.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
findable-ui 52.1 makes oauthprovider a discriminated union keyed on a new `flow` field (oauth_flow.authorization_code | oauth_flow.implicit), replacing the previous truthiness check on `authorize`. set the flow explicitly on every provider: anvil-cmg/dev keeps authorize and gets authorization_code; the other five (anvil-cmg cc-dev/prod/tempdev, hca-dcp cc-ma-dev/ma-prod) get implicit. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Contributor
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 7 out of 8 changed files in this pull request and generated 2 comments.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
NoopDog
approved these changes
May 5, 2026
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.
Summary
anvil-cmg/devto the OAuth 2.0 authorization code flow against Azul's new/user/authorizeendpointCLIENT_IDto anvildev's value (per @hannes-ucsc's Slack note) and adds anauthorizeURL on the provider, picked up by findable-ui's new code-flow branchauthorizethrough the provider configdev/anvildevshould adopt this for now; prod is unchangedBlocked by: findable-ui#905 — needs to merge and release before this can ship (
OAuthProvider.authorizefield comes from there).Closes #4793.
Test plan
localhost:3000against anvildev (via local findable-ui tarball): POSThttps://service.anvil.gi.ucsc.edu/user/authorizereturns{access_token, id_token, scope, expires_in, token_type}; profile loads@databiosphere/findable-uito the release containing Support for clarifying requirements around a single top level metadata version #905 before marking ready for reviewauthorizefield isn't in the published package yet)