Client Management

Taco’s core feature: a unified UI over your provider’s client (application) API.

Clients list

The clients page (/clients) lists every OAuth2/OIDC and SAML client known to the configured provider, with filtering and pagination.

Client detail

The client detail page (/clients/[id]) lets you edit:

• Basic info — name, description, logo
• Grant types and token endpoint authentication method
• Redirect URIs, scopes, and audience
• SAML-specific fields (ACS URL, entity ID, signature algorithm) when supported by the provider
• Custom metadata

Clone a client

From a client’s detail page, click Clone. Taco copies the full configuration into a new client, letting you rename it and adjust fields before saving — useful for spinning up staging/prod pairs of the same app.

Resource servers

The resource servers page (/resource-servers) manages the APIs (audiences) that clients can request access to, and their available scopes.

Note

Not every provider exposes a native resource server API. Where it doesn’t (Ory Hydra, RFC 7592), Taco derives the resource server list from the audiences and scopes already in use across existing clients — this list is read-only.

Provider support matrix

Feature	Ory Hydra	Auth0	Azure Entra ID	RFC 7592
OAuth2/OIDC clients	✅	✅	✅	✅
SAML clients	❌	❌	✅	❌
Native resource servers	❌	✅	❌	❌
Client cloning	✅	✅	✅	⚠️ Provider-dependent

See the Providers section for setup and provider-specific notes.