Account and node credentials
Model API keys, application authorizations, node secrets, and enterprise tokens serve different identities. Manage each with its owning service; disconnecting one account does not revoke unrelated credentials.
Locate the connection
Find model credentials under Settings > AI services and the specific connection instance. Find application accounts in plugin details. Inspect manual MCP URLs, headers, and environment in its server editor. A connection name alone does not establish account identity.
For planned rotation, create replacement credentials at the provider, update retained connections and validate, then revoke the old credential and confirm invalidation. For a leak, block the old secret first. Revoke OAuth grants through the provider's application authorization management; changing a model API key does not revoke an application grant.
Accept a credential update
Use a read-only request to verify the new account and target, then confirm provider-side revocation of the old credential. Record service, connection name, outcome, and affected jobs without secret values. Pause dependent work on authentication failure; inspect instance, account, endpoint, and permissions instead of pasting secrets into chat.
See AI services, app connections, and MCP servers. Node identity details below apply to standalone Evolver, not ordinary Desktop account maintenance.
Identify purpose
For model keys, check endpoint, account, model access, and billing. For application authorization, check connection instance, account, resource scope, and provider grants. For node secrets, identify the Hub and all consuming processes. For enterprise tokens, check endpoint, organization, and managed access policies.
A node ID is an identifier; node_secret is a secret. Exclude secrets from repositories, command history, screenshots, ordinary archives, and diagnostics. Inspect MCP environment variables and headers before sharing configuration.
Rotate or revoke
- Identify all connections and processes using the credential.
- Use the planned-rotation or incident-containment sequence above and update retained connections.
- Restart consumers of the old credential and verify identity with a read-only request.
- Confirm server-side invalidation. Deleting local configuration does not replace revocation.
If a leak is suspected, stop relevant external actions, record time and account or node ID, and preserve redacted evidence. Do not recover plaintext credentials from old logs.