LinkedIn Login Is Not an API Key: Using OpenID Connect the Right Way
Treat LinkedIn Sign In as standard OpenID Connect, not a permanent access token. Verify the ID token, key accounts by sub, and handle missing email gracefully.
ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Treat LinkedIn Sign In as standard OpenID Connect, not a permanent access token. Verify the ID token, key accounts by sub, and handle missing email gracefully.
Choose between a long-lived PyPI API token and Trusted Publishing (OIDC) for CI/CD package uploads, with trade-offs, a GitHub Actions example, and validation steps.
Static AWS keys in GitHub secrets are hard to rotate and expose a large blast radius. This post explains how to replace them with short‑lived OIDC tokens, walks through an AWS setup, shows a real workflow, and discusses trade‑offs.
A decision guide for picking between OpenID Connect and SAML 2.0 when connecting third-party apps to Okta, with a comparison table, protocol trade-offs, and validation steps for JWT claims and SAML assertions.
A decision guide for Deta Space apps: compare built-in Space Auth against custom OIDC/JWT stacks, understand sandbox constraints, and validate both paths with the Space CLI.
Stop storing long-lived PyPI tokens in your CI/CD secrets. Learn how to use Trusted Publishers and OIDC to establish a secure, identity-based publishing workflow.
Stop storing long-lived cloud keys in GitHub Secrets. Learn how to use OIDC federation to exchange short-lived GitHub tokens for temporary cloud credentials.
Long-lived PyPI API tokens in CI are a standing risk. Trusted Publishing uses OpenID Connect to issue short-lived, workflow-scoped credentials automatically—here is how to wire it up and what to watch for.
Learn how PyPI’s Trusted Publishing uses OIDC to replace static tokens in CI/CD pipelines, with a step‑by‑step GitHub Actions example, trade‑offs, and a quick verification checklist.