Ori Harness cookbook brings MDM, keyless auth
OpenRouter’s new cookbook shows teams how to deploy Ori Harness through MDM and let engineers authenticate with OIDC instead of storing long-lived API keys. The setup supports Claude Code, Codex, and other approved coding agents while enforcing organization-level policies.
This is a meaningful enterprise hardening step for AI coding agents, moving credential management from individual laptops into centralized identity and device policy.
- –OIDC access tokens expire after roughly 24 hours, sharply reducing the blast radius of stolen credentials
- –MDM policies can restrict sign-in methods, organizations, workspaces, and approved agent harnesses
- –Jamf, Kandji, Intune, Linux, and Windows deployment paths make the workflow practical for mixed fleets
- –Existing API keys are not automatically deleted, so teams still need a cleanup and revocation step
- –The protection is not absolute: Ori still stores a session, and unsigned releases remain a local security concern
DISCOVERED
10m ago
2026-11-05
PUBLISHED
28m ago
2026-11-05
RELEVANCE
AUTHOR
OpenRouter