# How we built Render OIDC

DevFeed: [How we built Render OIDC](<https://devfeed.tech/articles/how-we-built-render-oidc-122096.md>)

Original publisher: [Read original article](<https://render.com/blog/how-we-built-render-oidc>)

Published: 2026-11-06T22:34:00Z

Content type: article

Language: en

Sources: [Render](<https://devfeed.tech/sources/render.md>)

Topics: [OpenID connect (OIDC)](<https://devfeed.tech/topics/oidc.md>), [Access Control](<https://devfeed.tech/topics/access-control.md>), [Secret Scanning](<https://devfeed.tech/topics/secret-scanning.md>)

Tags: [anthropic](<https://devfeed.tech/tags/anthropic.md>), [api](<https://devfeed.tech/tags/api.md>), [api-keys](<https://devfeed.tech/tags/api-keys.md>), [application](<https://devfeed.tech/tags/application.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-iam](<https://devfeed.tech/tags/aws-iam.md>), [aws-sdk](<https://devfeed.tech/tags/aws-sdk.md>), [complex](<https://devfeed.tech/tags/complex.md>), [configure](<https://devfeed.tech/tags/configure.md>), [connect](<https://devfeed.tech/tags/connect.md>), [container](<https://devfeed.tech/tags/container.md>), [containerized](<https://devfeed.tech/tags/containerized.md>), [credentials](<https://devfeed.tech/tags/credentials.md>), [cryptographic](<https://devfeed.tech/tags/cryptographic.md>), [custom](<https://devfeed.tech/tags/custom.md>), [easy](<https://devfeed.tech/tags/easy.md>), [oidc](<https://devfeed.tech/tags/oidc.md>), [render](<https://devfeed.tech/tags/render.md>), [tokens](<https://devfeed.tech/tags/tokens.md>)

## AI overview

Render OIDC lets services authenticate to providers such as AWS and GCP with signed, short-lived tokens instead of long-lived API keys. Tokens expire after 60 minutes; subject claims can scope access by service, environment, or workspace, while workspace-specific issuer URLs limit cross-workspace acceptance even if a provider's subject checks are misconfigured. Audience claims bind each token to its intended provider. Since common SDKs generally read tokens from files and do not offer a consistent refresh endpoint, Render runs an OIDC Daemon outside each container. A read-only bind mount exposes a shared in-memory directory to the service; the daemon writes token files before startup and refreshes them periodically. Provider setup differs: AWS uses an environment variable pointing to its token file, while GCP needs a credential configuration file. The workspace-specific issuer safeguard means customers with multiple workspaces must configure each one separately.

## Source excerpt

Learn how Render built OIDC authentication using short-lived tokens, workspace-specific issuers, and a daemon that keeps credentials fresh.