a6-plugin-openid-connect

Configure APISIX routes to enforce OpenID Connect authentication.

1|2|Updated Mar 6, 2026
One-click install
npx skills add https://github.com/api7/a6 --skill a6-plugin-openid-connect-api7
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: a6-plugin-openid-connect
Source: https://github.com/api7/a6/tree/main/skills/a6-plugin-openid-connect
Command: npx skills add https://github.com/api7/a6 --skill a6-plugin-openid-connect-api7

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Configure APISIX to enforce OpenID Connect authentication and streamline integration with external IdPs.

Core Features & Use Cases

  • Integrates with enterprise IdPs (Keycloak, Auth0, Okta, Azure AD) for browser-based login and token verification.
  • Supports bearer-only mode, session management, PKCE, and Redis-backed sessions for scalable deployments.
  • Flexible configuration via client_id, client_secret, discovery URL, redirect URIs, and token verification options.

Quick Start

Configure a route with the openid-connect plugin using your IdP's discovery URL and client credentials to enable OIDC protection.

Frequently Asked Questions about a6-plugin-openid-connect

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

FAQPage Schema
How do I configure APISIX OpenID Connect authentication with an external IdP?▼

Configuring APISIX OpenID Connect involves applying the plugin to a route with your IdP's discovery URL, client_id, and client_secret to enforce browser-based login and token validation across enterprise integrations.

Does APISIX OpenID Connect support Keycloak, Okta, and Azure AD integrations?▼

Yes, APISIX OpenID Connect integrates with enterprise IdPs like Keycloak, Okta, Azure AD, and Auth0 to handle browser-based login, token verification, and session management across protected routes.

Can I use bearer-only mode and Redis-backed sessions for APISIX OIDC?▼

Yes, APISIX OIDC supports bearer-only mode for token validation without browser redirects and Redis-backed sessions for scalable deployments, alongside optional PKCE, JWKS, and token introspection configurations.

What do I need to set up APISIX openid-connect plugin for route protection?▼

Setting up the APISIX openid-connect plugin requires your IdP's discovery URL, client credentials, and redirect URIs, alongside optional session and token introspection configurations for route protection.

When should I use bearer-only mode versus browser-based login in APISIX OpenID Connect?▼

Use bearer-only mode in APISIX OpenID Connect for API token validation without browser redirects, while browser-based login provides interactive authentication and session management for web application routes.