Skip to content
AuthProxy

Try the hosted demo

Use the public demo to see AuthProxy’s end-user, administrator, and observability surfaces without installing anything.

Start at demo.authproxy.net. The environment is shared and may be reset, so never enter real credentials, customer data, or other private information.

How the demo sign-in works

Section titled “How the demo sign-in works”

AuthProxy is designed to use the host application’s identity. The demo has no host product, so the Demo Shell stands in for one:

  1. You choose an AuthProxy surface to explore.
  2. For the Marketplace, you choose the demo user who will own the connection; the Admin UI always uses the demo administrator.
  3. The shell signs a short-lived, one-time JWT identifying that actor.
  4. The browser is redirected to the Marketplace or Admin UI with the token.
  5. AuthProxy validates the signature and exchanges the token for a UI session.
sequenceDiagram
    actor User
    participant Shell as Demo host application
    participant UI as Marketplace or Admin UI
    participant AP as AuthProxy

    User->>Shell: Choose a demo journey and actor when needed
    Shell->>Shell: Sign nonce JWT for actor
    Shell-->>UI: Redirect with authToken
    UI->>AP: POST /session/_initiate
    AP->>AP: Verify signer, nonce, actor, and scope
    AP-->>UI: Session cookie and UI configuration

demo-admin is a pre-provisioned, self-signing administrator. demo-user is provisioned through the API, while its subject-only JWT is signed by the host’s system JWT key. Every Fresh user launch generates a new fresh-user-<uuid> external ID and provisions that actor from a full actor claim signed by the same host key.

Marketplace actors and connectors live in root.demo. Each user’s connections live in root.demo.<external_id>, so fresh users start empty and no demo user can see or operate on another user’s connections.

See host application integration for the production version of this handoff.

Marketplace

Section titled “Marketplace”

Choose Integration Marketplace in the Demo Shell, then choose Demo user to explore a preconfigured user or Fresh user to begin with an empty Marketplace. You can also visit the Marketplace directly if you already have a demo session.

Creating a connection in the Marketplace

The seeded catalog demonstrates five connector patterns:

Connector What to try
No auth See a catalog entry that needs no credential.
API key Enter demo-api-key; the test provider accepts only this intentionally fake key.
Basic OAuth Complete a normal authorization-code connection.
OAuth with tenant selection Enter a pretend tenant before the OAuth redirect.
OAuth with resource configuration Authorize first, then choose fake provider resources discovered through the new connection.

Create a fake OAuth account

Section titled “Create a fake OAuth account”

The OAuth examples connect to a dedicated go-oauth2-server test deployment, not Google, GitHub, or another real provider. Start any OAuth connector and use either:

  • seeded account demo-oauth-user@example.test with password demo-password; or
  • Register on the provider login page to create your own disposable account.

You can also choose Demo OAuth Provider in the Demo Shell to open its standalone test sign-in. Accounts and tokens exist only to exercise OAuth behavior in this test environment.

Admin UI

Section titled “Admin UI”

Choose Admin UI in the Demo Shell. It always opens as demo-admin.

Managing AuthProxy in the Admin UI

The Admin UI exposes namespaces, actors, connectors and immutable connector versions, connections, request events, background tasks and workflows, encryption keys, and rate limits.

Grafana

Section titled “Grafana”

Choose Telemetry in the Demo Shell, then select the Grafana view you want to open. Grafana has anonymous viewer access. The workspace includes:

Activity is shared and time-dependent. Generate a connection or proxy request, then adjust the dashboard time range if a panel is empty.

Next steps

Section titled “Next steps”