Skip to content

Use a token file for OIDC authentication - #326

Open
rob-race wants to merge 1 commit into
tailscale:mainfrom
rob-race:fix/oidc-token-file
Open

rob-race wants to merge 1 commit into
tailscale:mainfrom
rob-race:fix/oidc-token-file

Conversation

@rob-race

@rob-race rob-race commented Nov 9, 2026 •

Copy link
Copy Markdown

The authkey input is deprecated in favor of OAuth/OIDC. Callers that use a file-backed auth key to keep credentials out of process arguments cannot currently switch to the OIDC inputs without putting the JWT in --id-token.

Pass the OIDC token through a private temporary file using the CLI's existing --id-token=file:... support. Keep the file available during connection retries and remove it after success or failure. Existing workflow inputs, OAuth behavior and auth-key behavior stay the same.

Tests cover file permissions, cleanup on success/failure, and concurrent connections. Added them to the lint workflow and rebuilt dist/index.js.

Checked locally with Node 24: token-file tests, TypeScript typecheck, Prettier, actionlint and npm run build. Live tailnet integration tests need the upstream test environment and were not run locally. File-backed ID tokens are supported in Tailscale 1.90.1, the existing minimum for OIDC.

Signed-off-by: Rob Race <rob@upstate.cloud>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant