a2a-workflow

Configure Safeguard A2A certificate-based workflows in safeguard-ps.

24|35|Updated Sep 14, 2017
One-click install
npx skills add https://github.com/OneIdentity/safeguard-ps --skill a2a-workflow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: a2a-workflow
Source: https://github.com/OneIdentity/safeguard-ps/tree/main/.agents/skills/a2a-workflow
Command: npx skills add https://github.com/OneIdentity/safeguard-ps --skill a2a-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you set up and operate Safeguard PowerShell A2A integrations so you can authenticate with mutual TLS and reliably retrieve or update managed credentials without relying on bearer-token sessions.

Core Features & Use Cases

  • Certificate-based A2A registration and credential retrieval: Create A2A registrations, configure credential retrieval mappings, fetch the generated API key, and use it to call A2A endpoints with a client certificate.
  • Secret access and bidirectional updates: Retrieve passwords and SSH private keys (including selecting key formats) and support bidirectional secret updates where the registration is configured appropriately.
  • Brokering and event-driven handlers: Create access requests for other users and keep long-running handlers synchronized through SignalR event listening and higher-level password/SSH-key handler patterns.

Quick Start

Run Wait-SafeguardA2aEvent with your appliance address, A2A API key, and client certificate thumbprint to start receiving credential update events in real time.

Frequently Asked Questions about a2a-workflow

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I retrieve managed credentials using Safeguard A2A with mutual TLS?

You can use a client certificate for A2A credential retrieval by configuring mutual TLS authentication in safeguard-ps, fetching the generated A2A API key, and calling A2A endpoints with the certificate and API key header to retrieve passwords or SSH private keys.

What is the difference between certificate file, thumbprint, and in-memory certificate authentication for A2A?

Certificate file, thumbprint, and in-memory certificate are three mutual TLS authentication modes for A2A. They dictate how the client certificate is supplied during API key header authentication, offering flexibility in securely passing certificates for credential retrieval without bearer tokens.

How do I listen for credential update events in real-time using safeguard-ps?

To listen for credential update events, run Wait-SafeguardA2aEvent with your appliance address, A2A API key, and client certificate thumbprint. This synchronizes long-running handlers via SignalR events to trigger handler-driven re-fetch behavior.

Can I update secrets bidirectionally through an A2A registration?

Yes, you can perform bidirectional secret updates through an A2A registration when the registration is configured appropriately. This allows retrieving and updating passwords or SSH private keys, including selecting specific key formats, via the A2A workflow.

How does secret brokering work for other users in an A2A workflow?

Secret brokering in an A2A workflow works by creating access requests for other users through the A2A registration. This allows delegated credential retrieval and management without directly exposing the underlying managed passwords or SSH keys to the requesting user.