freeshard-oidc-identity-campaign

Integrate a native OpenID Connect provider into Shard Core for zero-click authentication.

47|2|Updated Feb 11, 2025
One-click install
npx skills add https://github.com/FreeshardBase/freeshard --skill freeshard-oidc-identity-campaign
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: freeshard-oidc-identity-campaign
Source: https://github.com/FreeshardBase/freeshard/tree/main/.claude/skills/freeshard-oidc-identity-campaign
Command: npx skills add https://github.com/FreeshardBase/freeshard --skill freeshard-oidc-identity-campaign

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires authlib, psycopg, fastapi.

What problem does it solve?

This skill provides a structured, phased campaign to integrate a native OpenID Connect provider into the Freeshard core, enabling seamless, passwordless authentication for installed applications.

Core Features & Use Cases

  • Zero-Click Authentication: Leverages existing terminal-pairing sessions to log users into apps like Immich automatically.
  • Secure Identity Management: Implements a robust, embedded Authlib-based IdP that avoids the overhead and configuration complexity of external IAM solutions.
  • Use Case: A user installs a new application on their Shard and accesses it for the first time, finding themselves already logged in as the owner without needing to enter credentials or perform manual setup.

Quick Start

Initiate the OIDC integration campaign by reviewing the spike branch and creating the intent specification on the project issue tracker.

Frequently Asked Questions about freeshard-oidc-identity-campaign

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

FAQPage Schema
How do I implement zero-click OIDC authentication for self-hosted apps?

Zero-click OIDC authentication leverages existing terminal-pairing sessions to automatically log users into first-party applications without entering credentials, using a native identity provider integrated directly into the core system.

What's the best way to manage OIDC client registration and token issuance in FastAPI?

OIDC client registration and token issuance in FastAPI are managed via an embedded Authlib-based identity provider, handling the full lifecycle from secure provisioning to terminal-linked token revocation.

Does this native identity provider enforce PKCE-S256 and private JWKS for OpenID Connect?

Yes, the native OpenID Connect provider enforces strict security requirements including PKCE-S256 enforcement and zero-leak JWKS privacy to ensure secure key management within a self-hosted environment.

Can I use Authlib to avoid external IAM complexity for single sign-on?

Yes, integrating Authlib as an embedded identity provider avoids the overhead and configuration complexity of external IAM solutions while enabling seamless single sign-on for installed applications.

How does terminal-linked revocation work for OIDC tokens?

Terminal-linked revocation binds issued OIDC tokens to active terminal-pairing sessions, automatically invalidating access when the originating terminal session is terminated or revoked.