Skip to main content
Unlisted page
This page is unlisted. Search engines will not index it, and only users having a direct link can access it.
Version: 11.3.0

Managing Service Agent Credentials

Overview​

A service agent credential lives in the systems you configured it into, so you need to be able to change or stop it quickly. In HYPR AgentPass™, every change on this page takes effect on the service agent's next request. There is nothing to restart and no cache to wait out. You touch the calling system only when you replace the credential itself.

note

Managing service agents needs a role that can manage service agents. Out of the box, only AgentPassAdmin can. See Service Agents.

The Credential Tab​

The Credential tab shows what a service agent can do, and is where you stop it. To open it, go to Oversight → Cloud Agents, click the service agent, and click the Credential tab.

FieldWhat it shows
Accountable ownerThe person accountable for the credential
Acts with roleThe ID of the role that governs the credential's calls
Connectors in scopeEverywhere the credential is accepted
May act as the owner onConnectors where it may use the owner's connected account
Credential expiresThe expiry, or Never
Retains request payloadsWhether AgentPass keeps request and response bodies for this service agent

The tab also holds Edit, for changing any of these, and Rotate credential.

Change What a Service Agent May Reach​

Click Edit to change the role, the connectors in scope, the owner, the expiry, the act-as-owner opt-in or payload retention. Editing does not change the credential itself, so the calling system keeps working with no update.

Narrowing takes effect immediately. Remove a connector from the scope, and the next call to it is refused. Change the role, and the next request sees a different set of offered and permitted tools.

Rotate a Credential​

Rotating issues a new credential and stops the old one at once. Rotate when:

  • The credential may have been exposed, or was copied somewhere you did not intend
  • The person who configured it leaves
  • Your organization's schedule for secrets calls for it

To rotate:

  1. On the Credential tab, click Rotate credential.
  2. Confirm. The current credential stops working immediately.
  3. Copy the replacement from the dialog. As at creation, AgentPass shows it only once.
  4. Update the calling system with the new credential.
No overlap period

The moment you rotate, calls with the old credential are refused. The calling system stops working until you configure the new one. Before you start, have somewhere to paste it and access to update the caller, or plan the rotation for a window where a gap is acceptable.

Disable a Service Agent​

Disabling is the fast stop. Use the service agent's enable control on the Cloud Agents page or on its detail page. Its next call is refused, immediately, from every caller holding the credential. Turning it off asks for an optional reason, as for any agent. See Enabling and Disabling.

Disabling keeps the service agent, its configuration and its activity history. Use it when calls must stop while you investigate. Enable the service agent again, and the same credential works again.

Let a Credential Expire​

A credential with an expiry stops working when that time passes. The console then flags the service agent as needing attention, and its Credential tab shows the expiry has passed. An integration that stopped quietly is therefore visible.

From there, you can either:

  • Extend the expiry with Edit. The same credential works again.
  • Click Rotate credential to issue a fresh credential with a new expiry.

Reviewing Your Service Agents​

A service agent keeps working without anyone signing in, so review your service agents deliberately:

  • On a schedule. Confirm each one is still in use, still owned by the right person, and still scoped to the connectors it calls.
  • When someone leaves. A service agent keeps working after its accountable owner leaves your organization. Reassign the owner as part of offboarding. Check carefully any service agent permitted to act as that person on a connector.
  • When you add a connector. New tools arrive without access. Check whether the roles your service agents carry should reach them. See Controlling MCP Tool Access by Role.