fix: local-auth token mismatch + OAuth docs/help#30
Merged
Conversation
The compose builder re-ran configureAuthLocalEnv, minting a new API_SERVICE_TOKEN in auth/.env that no longer matched the one written to the API. Read the existing auth env instead. Also document the OAuth setup flow, the npm Automation-token requirement, and the templates-ref bump in AGENTS.md, and note OAuth provider setup in the help output.
Picks up the web Dockerfile casing fix so scaffolded projects build on case-sensitive filesystems.
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.
Session follow-ups.
Fix: local auth mode service-token mismatch
With
authMode: local,configureAuthLocalEnvran a second time (via the compose builder) and minted a freshAPI_SERVICE_TOKENinauth/.env, so it no longer matched the token written to the API when running services outside Docker. The compose builder now reads the already-written auth env (extractSharedFromExistingEnv) instead of regenerating it. Docker mode (the default) was unaffected.Docs / help
setup.oauth-> provider prompts ->buildAuthEnv), the npm Automation-token requirement for publishing (a granular token returns a confusingE404), and the templates-ref bump dance.seamless --help: note that--oauthprompts for OIDC providers and wires them in.