Skip to content

Overview

SSO for SSH. Two audiences share this surface:

  • The client (ssoossh, and pam_ssoossh) creates certificate requests and waits on the result over SSE. These endpoints are unauthenticated: a request’s ID is an unguessable UUID and is itself the capability, and authorization happens at the approval step.
  • The web UI reads and approves. Everything under a session cookie.

Every JSON body this API emits is the {data, error} envelope from .claude/rules/server-api.md — success and error, client-facing and web-UI-facing, including the data of each server-sent event. One decode path, no exceptions to remember.

This file is generated from Go annotations by make openapi. Edit the handlers, not the YAML.

ssoossh documentation

Information

  • License: MIT
  • OpenAPI version: 3.1.0

The fleet API key’s secret, shown once when the key is created or rotated. Sent with the id on every NSS lookup; the server removes it from the request before anything is logged.

Security scheme type: apiKey

Header parameter name: X-Ssoossh-Key-Secret