pocket-id-provider

Deploy Pocket-ID with persistent storage and configure OIDC clients for passkey authentication.

Updated Oct 31, 2024
One-click install
npx skills add https://github.com/thesammykins/dotfiles --skill pocket-id-provider
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pocket-id-provider
Source: https://github.com/thesammykins/dotfiles/tree/main/.agents/skills/pocket-id-provider
Command: npx skills add https://github.com/thesammykins/dotfiles --skill pocket-id-provider

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pocket-ID provides a secure, passkey-first identity layer for self-hosted apps, simplifying login and user management without passwords.

Core Features & Use Cases

  • Deploy pocket-id/pocket-id with persistence.
  • Configure OIDC Clients (Client ID, Secret, Redirect URIs).
  • Setup Passkey (WebAuthn) users.
  • Integrate Pocket-ID with Traefik (Forward Auth) or App Services.

Quick Start

Deploy Pocket-ID, configure a generic OIDC client, and enable a first admin passkey.

Frequently Asked Questions about pocket-id-provider

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

FAQPage Schema
How do I set up passkey authentication for self-hosted apps?

You can set up passkey authentication for self-hosted apps by deploying Pocket-ID to provide a secure, passwordless identity layer using WebAuthn. It simplifies login by allowing users to authenticate with passkeys instead of traditional passwords.

What is needed to configure OIDC clients for passwordless SSO?

Configuring OIDC clients for passwordless SSO requires a deployed Pocket-ID instance with a persistent backend, a secure HTTPS domain, and a public URL to register Client IDs, secrets, and redirect URIs for your services.

Can I use Traefik Forward Auth with Pocket-ID for single sign-on?

Yes, you can use Traefik Forward Auth with Pocket-ID to enable single sign-on. Pocket-ID integrates with Traefik to secure your self-hosted apps, applying passkey-based identity verification across multiple services.

Do I need a public HTTPS domain to deploy a WebAuthn identity provider?

Yes, a secure HTTPS domain and a public URL are required to deploy this WebAuthn identity provider. Pocket-ID needs this secure context to operate properly and manage passkey authentication safely.

How do I add an admin passkey when setting up SSO for self-hosted apps?

To add an admin passkey when setting up SSO, deploy Pocket-ID with persistence, configure a generic OIDC client, and then enable your first admin passkey through the WebAuthn setup process.