feat: Add OPA (Okta Privileged Access) secret management integration #4
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Integrates Okta Privileged Access (OPA) for secure LLM credential management, replacing plain-text
.envfile storage with enterprise-grade secret management.Problem
Before this integration, LLM credentials were stored in
.envfiles:Solution
OPA provides enterprise-grade secret management:
Architecture
Changes
New Files
scripts/lib/opa-api.tsscripts/setup-opa-secrets.tsscripts/validate-opa-secrets.tspackages/agent0/src/secrets/opa-api.tspackages/agent0/src/secrets/opa-secrets.tsdocs/opa-secret-management.mdModified Files
packages/agent0/src/agent.tspackages/agent0/package.jsonjosedependency for JWE.gitignore.env.opaAdditional Scripts
bootstrap-okta-tenant.jsrollback-okta-config.jsvalidate-okta-config.jsUsage
Setup (one-time)
Runtime
Agent0 automatically:
.env.opaexists)Configuration
.env.opaexample:Documentation
See docs/opa-secret-management.md for full implementation details.