Credential Management¶
Credential Management stores reusable secrets for remote onboarding, SSH/WinRM automation, scheduled Ansible, and Borealis service tokens. Aegis Cipher protects stored secret material at rest.
Add Credential¶
- Open
Access Management > Credentials. - Select
New Credential. - Name the credential.
- Choose optional site scope.
- Pick credential type and connection type.
- Enter username and secret material.
- Add optional privilege escalation details.
- Save.
Pick Credential Scope¶
- Site-scoped credentials fit customer or lab boundaries.
- Global credentials should be rare and intentionally named.
- Scheduled jobs and onboarding use credential records by ID; secret material is not copied into job definitions.
Manage Aegis Cipher¶
Credentials page also shows Aegis status and runtime actions after bootstrap. Use rotation when changing the cipher intentionally. Force reset is disaster recovery and destroys stored secret material that cannot be decrypted.
Warning
Aegis force reset disables or marks credential-backed jobs until missing secrets are re-entered.
Detailed Codex Breakdown
API endpoints¶
GET /api/credentials- list credentials without secret material.GET /api/credentials/<credential_id>- get one credential without secret material.POST /api/credentials- create credential.PUT /api/credentials/<credential_id>- update credential.DELETE /api/credentials/<credential_id>- delete credential.GET /api/github/token- GitHub token status.POST /api/github/token- update GitHub token.
Related documentation¶
Source map¶
- Credentials API:
Data/Engine/Containers/api-backend/data/services/API/access_management/credentials.py - Aegis service:
Data/Engine/Containers/api-backend/data/services/aegis_cipher.py - Credentials UI:
Data/Engine/Containers/webui-frontend/data/web-interface/src/Access_Management/Credential_List.jsx - Credential editor:
Data/Engine/Containers/webui-frontend/data/web-interface/src/Access_Management/Credential_Editor.jsx
Runtime behavior¶
- Credential records live in
credentials. - Secret fields store
aegis:v1:envelopes after Aegis setup. - Job workers fetch decrypted credential material only at execution time through internal Engine paths.