Skip to content
IAM Insights

Explainers · Glossary

CI

continuous integration · CI pipeline

Continuous integration, the automated pipeline that builds and tests code on every change, usually paired with continuous delivery (CI/CD) to deploy it. Its runners and jobs hold credentials of their own, which makes them non-human identities.

In our briefings

The claim each of the newest briefings on CI would have you leave with.

  1. The WorkOS CLI writes its MCP server into a coding agent only when the user opts in: the setup offer it may show after workos auth login or workos install defaults to No and stops asking once declined, a non-interactive, CI or --json run installs nothing, and opting in takes an explicit command such as workos mcp install or workos setup --yes. Once connected, the agent acts as the person who signed it in. Paktiti writes that the agent "inherits your dashboard role and can only do what your account is allowed to do." It works against one environment at a time, starts in a sandbox environment, and operates on production only when the user tells it to. Teams that want tighter limits get three independent admin settings (Enable, Allow production access and Allow write access), and all three are on by default. Apart from those settings and the sandbox default, the post describes no way to give the agent less than the user's own role.

    Opt in to WorkOS's MCP server and your coding agent acts as you, with write and production access on by defaultBI-FIND-2026-2401

  2. The IETF datatracker shows that the IESG approved OAuth Identity and Authorization Chaining Across Domains (draft-ietf-oauth-identity-chaining) as a Proposed Standard on 22 June 2026, and that it has been in the RFC Editor's queue since that day. Revision 17, the text we read, was posted on 19 July 2026 during that editing. Its authors are Arndt Schwenkschuster and Pieter Kasselman of Defakto Security, Kelley Burgin of MITRE, Mike Jenkins of NSA-CCSS, Brian Campbell of Ping Identity and Aaron Parecki of Okta. Campbell co-wrote RFC 8693 and RFC 7523, the two RFCs the draft combines, and Parecki co-wrote RFC 9728, one of the ways it names for finding the other domain's authorization server. The working group's write-up for the IESG lists implementations, among them Keycloak 26.5 and Okta's. Two other drafts we have read point to it: the transaction-tokens draft leaves crossing domains to it, and the AI agent authentication draft says cross-domain access SHOULD use identity chaining.

    OAuth's draft for crossing trust domains is approved for publication and never says agentBI-FIND-2026-0184

  3. Woven by Toyota's AI agent sits at a new third step of the company's security-exception review, ahead of the human reviewer. Juan Corena says the outputs include a recommendation to approve, a recommendation to reject, or a request for more information with questions that may matter for granting it, and once the agent judges it has enough information the ticket goes to a human. His reason: "eventually a human needs to take the responsibility and understand all the consequences of what is being done there." He adds that simply asking whether a request complies with the standards would always get "no", since that is why it was requested, so the design had to allow for it.

    Woven by Toyota's exception agent recommends; a person decides, because a human has to answer for itBI-FIND-2026-2242

›Cited in 15 briefings

Every briefing that discusses this term, newest first.

  1. Opt in to WorkOS's MCP server and your coding agent acts as you, with write and production access on by default

    Article · · WorkOS · Maria Paktiti · Sep 30, 2026

  2. OAuth's draft for crossing trust domains is approved for publication and never says agent

    Draft · · IETF OAuth Working Group · Arndt Schwenkschuster et al. · Jul 19, 2026

  3. Woven by Toyota's exception agent recommends; a person decides, because a human has to answer for it

    Video · · Agentic AI Foundation · Uploaded November 4, 2026

  4. LiteLLM left a leaked admin key live; its first reported use, 136 days on, yielded an org owner's GitHub token

    Article · · LiteLLM blog · Oliver Jensen et al. · Oct 23, 2026

  5. Anthropic's Osmani: Claude reviews a change first, people check its evidence, and a named owner stays on the hook

    Video · · AI Engineer · Uploaded October 28, 2026

  6. NovaFabric seals AI agent runs as signed evidence, and its author says a signature proves a key, not a person

    Paper · · arXiv · Mohsen Seyedkazemi Ardebili · Oct 25, 2026

  7. SailPoint’s JIT demo separates approved eligibility from expiring activation

    Video · · SailPoint · Oct 16, 2026

  8. Shai-Hulud v4 used an MCP tool description to tell AI assistants to read SSH keys and keep quiet about it

    Video · · OWASP Foundation · Uploaded October 22, 2026

  9. Mozilla's AI bug hunting got past hallucinated reports once a harness checked each finding mechanically

    Video · · OWASP Foundation · Uploaded October 21, 2026

  10. Agents exceeded the user's authorization in 19.2% of a benchmark's runs, more under benign pressure than attack

    Paper · · arXiv · Zhiping Zhang et al. · Oct 20, 2026

  11. Auth0's own Claude Code tutorial runs the agent on the developer's login and hands it fifteen admin scopes

    Article · · Auth0 Blog · Manish Hatwalne · Sep 29, 2026

  12. Sierra's cloud agent runs 75,000 sessions a month and never holds a credential

    Article · · Sierra Engineering · Allen Chen et al. · Jul 15, 2026

  13. One implementer found a transaction-token rule that let any scope through; the OAuth group fixed it in weeks

    Draft · · IETF Datatracker · Dhruv Agnihotri · Jun 23, 2026

  14. In a stress test, Claude Code made changes through file edits that auto mode's permission check never sees

    Paper · · arXiv · Zimo Ji et al. · Apr 4, 2026

  15. A code scanner's top find in 583 MCP servers was hard-coded keys; tool poisoning needed an MCP-specific scanner

    Paper · · arXiv · Mohammed Mehedi Hasan et al. · Jun 16, 2025