fix(cli): pass api_url to UI for OAuth to ensure same backend is used #22
Conversation
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
The CLI uses the correct default API URL (postgres.ai/api/general/) which successfully creates OAuth sessions. The "OAuth session not found" error appears to be a backend issue where the UI at console.postgres.ai cannot find sessions created by the API. Changes: - Add comprehensive unit tests for URL resolution and auth components - Add CI smoke test to verify OAuth endpoint is reachable - Clean up README examples to distinguish production vs staging environments Note: The actual OAuth issue requires backend investigation - the API and UI services may not be sharing session storage properly.
When user has a custom apiBaseUrl in config (e.g., staging v2.postgres.ai), the CLI now passes this URL to the UI via api_url query param. This ensures oauth_approve is called on the same backend where oauth_init created the session, preventing 'OAuth session not found' errors due to API/UI backend mismatch.
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.
Problem
Fixes https://gitlab.com/postgres-ai/platform/-/issues/370
When a user has a custom
apiBaseUrlin their CLI config, OAuth authentication fails with "OAuth session not found" because CLI and UI hit different backends.Root Cause
oauth_initon configured API (e.g., stagingv2.postgres.ai) → session created thereoauth_approveon its default API (productionpostgres.ai) → session NOT foundSolution
Pass
api_urlparameter to the UI so it callsoauth_approveon the same backend whereoauth_initcreated the session.Related