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
OIDC | |
You're a cybersecurity expert in a major tech company. A software developer asks for advice on his idea to export user's oidc token to the operating environment of his orchestration software. What would you say? | |
TL;DR | |
Don’t export end-user OIDC tokens into the orchestration host environment. It’s high risk: easy to leak, reuse, and escalate. Use short-lived, audience-restricted machine identities or a token-exchange/backchannel pattern (workload identity, Vault, cloud STS, OAuth2 token exchange) and keep tokens out of environment variables. Harden with minimal scopes, short TTLs, mTLS/proof-of-possession, and strong auditing if you must. | |
⸻ |