Use production WorkOS client ID for CLI login - #58
Merged
Merged
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
The CLI currently defaults to the placeholder
client_cronitor_cli, socronitor auth logincannot use the production WorkOS application without an environment override. Replace it with the production Public Connect client ID matching the server'sprod.mcp-workos.cli-client-idvault setting.The client ID is a public OAuth identifier. Existing environment and build overrides retain their precedence.
Validation in Docker with Go 1.26.2: the regression test fails with the placeholder and passes with the production ID;
go test ./cmd ./libpasses.go vet ./cmd ./libreports existing unkeyedTimezoneLocationNameliterals incmd/root.go(unchanged by this PR).