Answer: Devin's OIDC authentication works by giving every Devin session a short-lived identity token signed by Devin and refreshed for the lifetime of the session; your cloud provider verifies the token against Devin's public OIDC issuer and grants temporary, scoped access, so tokens expire automatically with nothing to rotate or revoke. Status: Confirmed Entry: tool/devin/permissions-and-security/how-oidc-works Revision: 1 Digest: sha256:57d58c3abd619775 (changes whenever the content changes) Timeline: Created: 2026-11-13T03:15:44Z Last changed: 2026-11-13T03:15:44Z Last verified: 2026-11-20T12:47:49Z Next check: 2026-11-21T12:47:49Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of token type | identity token | [1] | 2026-11-20 token lifetime | short-lived | [1] | 2026-11-20 token refresh | refreshed for the lifetime of the session | [1] | 2026-11-20 verification | Devin's public OIDC issuer | [1] | 2026-11-20 claims | org_id | [1] | 2026-11-20 expiration | Tokens expire automatically | [1] | 2026-11-20 Sources: [1] Cognition. "Cloud Authentication with OIDC". https://docs.devin.ai/product-guides/oidc.md Role: primary. Accessed: 2026-11-20T12:47:49Z Quote: "Every Devin session automatically receives a short-lived **identity token**" (Supports: token type) Quote: "automatically receives a short-lived **identity token**" (Supports: token lifetime) Quote: "signed by Devin and refreshed for the lifetime of the session" (Supports: token refresh) Quote: "Your cloud provider verifies the token against Devin's public OIDC issuer and grants temporary, scoped access." (Supports: verification) Quote: "Tokens identify the session through claims such as `org_id`, `devin_id`, and `requesting_user_email`" (Supports: claims) Quote: "Tokens expire automatically — there is nothing to rotate or revoke." (Supports: expiration) Published: 2026-11-20T09:56:08Z Snapshot SHA-256: dd4071ae05923ac481e37787594786ba1f9c6fa9cb8f54bf057d34f11a341b08 (captured 2026-11-13T03:15:43Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. On this check the text of [1] was unchanged since 2026-11-13T03:15:44Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T12:47:49Z. No independent second source is configured for this entry Last successful check: 2026-11-20T12:47:49Z Last attempt: 2026-11-20T12:47:49Z Notes and limitations: Extracted automatically from a single official source (section "How it works"). Related: https://latestn.com/tool/devin/permissions-and-security/imessage-link-permissions What permissions do I need to link a Devin Bot to iMessage? https://latestn.com/tool/devin/permissions-and-security/ip-allowlisting What IP addresses do I need to allowlist for Devin? https://latestn.com/tool/devin/permissions-and-security/list-models-auth-requirements What API key and permissions do I need to list Devin Desktop models and pricing? https://latestn.com/tool/devin/permissions-and-security/endpoint-permissions Which permissions does each Devin Desktop API endpoint require? https://latestn.com/tool/devin/permissions-and-security/gitlab-repository-permissions What repository permissions does Devin need for GitLab, and how do they differ for Core, Teams, and Enterprise users? https://latestn.com/tool/devin/permissions-and-security/give-credentials How do I give Devin credentials to sign in to tools? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-13T03:15:44Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/devin/permissions-and-security/how-oidc-works/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/devin/permissions-and-security/how-oidc-works POST: https://latestn.com/dispute/tool/devin/permissions-and-security/how-oidc-works with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/devin/permissions-and-security/how-oidc-works?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How does Devin's OIDC authentication work without storing static credentials? Revision 1, last verified 2026-11-20T12:47:49Z. https://latestn.com/tool/devin/permissions-and-security/how-oidc-works (accessed 2026-11-21T10:03:58Z). @misc{LatestN_tool_devin_permissions_and_security_how_oidc_works_r1, title = {How does Devin's OIDC authentication work without storing static credentials?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/devin/permissions-and-security/how-oidc-works}}, note = {Revision 1; digest sha256:57d58c3abd619775; last verified 2026-11-20T12:47:49Z; accessed 2026-11-21T10:03:58Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/devin/permissions-and-security/how-oidc-works