auth-identity
v0.3.4End-user authentication & identity team — agents (auth-architect, auth-implementation-engineer) for adding login to a web app (React/Next), an API, and a dashboard. Methods: Google/Apple/Microsoft/GitHub social SSO, magic link, passkeys/WebAuthn, email+password — via managed auth (leaning Supabase Auth). skills, templates, a best-practices index, a scenarios bank (unverified field notes), an advisory anti-pattern hook, a stdlib JWT/scope/cookie analyzer (scripts/auth_analyze.py), and a web-verified knowledge bank with Mermaid decision trees (build-vs-buy, which-providers, OAuth-flow, token-storage, gate-the-dashboard, logout, refresh-reuse, MFA-factor, step-up auth). House rules: Authorization Code + PKCE never Implicit; never store tokens in localStorage; validate ID tokens server-side. Boundary: AUTHENTICATES the person; data-platform AUTHORIZES the data (RLS/embed-JWT); Entra seams to azure-cloud, auth code to security-reviewer. Requires ravenclaude-core@>=0.7.0.
By Matt CorbettLicense: MIT7 GitHub starsUpdated last week
Directory evidence
- Runtimes
- Claude Code
- Parsed components
- 7 skill or MCP entries
- Source updated
- Sep 15, 2026
- Manifest status
- Canonical path parsed
The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →
Install auth-identity for Claude Code
claude plugin marketplace add IchenDEV/agent-plugin-mkt
claude plugin marketplace update agent-plugin-marketplace
claude plugin install auth-identity@agent-plugin-marketplacePaste and run these commands in a terminal with Claude Code. They add and refresh the PluginsMP catalog, then install this plugin.
The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.
Get the source manually
git clone https://github.com/mcorbett51090/RavenClaudeClone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is plugins/auth-identity/.
Plugin files
├── .claude-plugin/plugin.json├── skills/add-an-auth-provider/SKILL.md├── skills/authorization-rbac/SKILL.md├── skills/gate-the-dashboard/SKILL.md├── skills/google-sso-setup/SKILL.md├── skills/oauth-oidc-flow-design/SKILL.md├── skills/protect-spa-and-api/SKILL.md└── skills/session-and-token-management/SKILL.md
Included Skills7
Add a login method to an existing Supabase Auth app — Apple, Microsoft, GitHub social SSO, plus magic link, passkeys (WebAuthn), or email+password. The generic enable-provider procedure with each provider's gotchas (especially Apple's expiring ES256 secret + first-login name capture). Generalizes google-sso-setup to the variety pack.
RBAC and ABAC in the application layer: defining roles and claims, mapping the authenticated identity to roles, enforcing roles in middleware and UI. The critical seam: row-level data scoping hands off to data-platform RLS via auth.uid(). Authentication proves identity; authorization controls access.
Put the analytics dashboard and embedded BI behind login: app-shell login gate + session check + the handoff to data-platform's embed-JWT and RLS for per-user data isolation. The clearest expression of the auth-identity → data-platform seam.
Wire Sign in with Google end-to-end: Google Cloud OAuth client + consent screen + redirect URIs + scopes, then via Supabase Auth's Google provider (and a note on the Auth.js / direct path). Step-by-step with verification checkpoints.
Pick and implement the right OAuth 2.0 / OIDC flow by client type: Authorization Code + PKCE for SPA and native apps, confidential-client code flow for server-side apps, client-credentials for M2M. ID-token vs access-token vs refresh-token handling. Deprecated Implicit flow is never recommended.
Protect a React/Next.js SPA with route guards and middleware, and protect an API with token-verification middleware (signature + iss + aud + exp). Covers CORS configuration and CSRF defense. Applies to both the web-app and the API/backend targets.
Session vs JWT trade-offs; HttpOnly+Secure+SameSite cookie storage; refresh-token rotation; logout and revocation; storage anti-patterns (no tokens in localStorage or sessionStorage). The post-sign-in half of the auth lifecycle.
Plugin manifests1
{
"name": "auth-identity",
"version": "0.3.4",
"description": "End-user authentication & identity team — agents (auth-architect, auth-implementation-engineer) for adding login to a web app (React/Next), an API, and a dashboard. Methods: Google/Apple/Microsoft/GitHub social SSO, magic link, passkeys/WebAuthn, email+password — via managed auth (leaning Supabase Auth). skills, templates, a best-practices index, a scenarios bank (unverified field notes), an advisory anti-pattern hook, a stdlib JWT/scope/cookie analyzer (scripts/auth_analyze.py), and a web-verified knowledge bank with Mermaid decision trees (build-vs-buy, which-providers, OAuth-flow, token-storage, gate-the-dashboard, logout, refresh-reuse, MFA-factor, step-up auth). House rules: Authorization Code + PKCE never Implicit; never store tokens in localStorage; validate ID tokens server-side. Boundary: AUTHENTICATES the person; data-platform AUTHORIZES the data (RLS/embed-JWT); Entra seams to azure-cloud, auth code to security-reviewer. Requires ravenclaude-core@>=0.7.0.",
"author": {
"name": "Matt Corbett"
},
"homepage": "https://github.com/mcorbett51090/RavenClaude",
"license": "MIT",
"keywords": [
"authentication",
"identity",
"oauth",
"oidc",
"sso",
"google-sso",
"sign-in-with-apple",
"passkeys",
"webauthn",
"magic-link",
"supabase-auth",
"session",
"jwt",
"pkce",
"rbac",
"csrf"
],
"requires": {
"plugins": [
"ravenclaude-core@>=0.7.0"
]
}
}For maintainers
If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.
[auth-identity on Agent Plugins Marketplace](https://pluginsmp.com/plugins/auth-identity)