Passokey is a self-hosted Passkey (WebAuthn/FIDO2) authentication server with multi-client SSO support.
- Passwordless authentication using Passkeys (WebAuthn/FIDO2)
- Multi-client architecture with SSO support
- Easy JWT-based integration with existing applications
- Standard OpenID Connect (OIDC) integration with existing applications
- User permission management per client
- Admin panel for managing clients, users, and permissions
The documentation is available at docs folder.
{
"BaseUrl": "",
// Site URL (e.g., "https://auth.example.com")
"AppName": "",
// Site name displayed to users
"Session": {
"IdleTimeoutMinutes": 0,
// Session cleanup time after no activity
"AuthorizedClientLifetimeMinutes": 0,
// How long a user session remains valid after login
"AdminSessionLifetimeMinutes": 0
// How long an admin session remains valid after login
},
"Fido2": {
"ServerDomain": "",
// Your domain (e.g., "example.com")
"ServerName": "",
// Display name shown in passkey prompt
"Origins": [],
// Additional allowed origins (BaseUrl is included automatically)
"TimestampDriftTolerance": 0,
// Allowed time difference (ms) between client and server clocks for authenticator timestamp validation
"UserVerification": ""
// User verification requirement: "Required", "Preferred", or "Discouraged"
},
"Jwt": {
"TokenLifetimeMinutes": 0
// JWT token validity period; typically used by callback URL to create a real session
}
}Download appsettings.json to data folder and configure it, then start with docker-compose.yaml:
curl -O https://raw.githubusercontent.com/mahelbir/passokey/main/docker-compose.yaml
curl --create-dirs -o data/appsettings.json https://raw.githubusercontent.com/mahelbir/passokey/main/Application/appsettings.json
nano data/appsettings.json
docker compose up -d
Requirements:
git clone https://github.com/mahelbir/passokey.git
cd passokey
# Copy and configure appsettings.json
cp Application/appsettings.json Application/appsettings.Production.json
nano Application/appsettings.Production.json
# Publish and run the application
dotnet publish -c Release -o publish
publish/Application --environment ProductionVisit admin panel at http://localhost:4050/admin
For production environments, you should expose Passokey behind a reverse proxy with HTTPS:
- Nginx / Apache - Traditional reverse proxy setup
- Cloudflare Tunnel - Zero-config secure tunnel without opening ports
- Traefik - Docker-native reverse proxy with automatic SSL
- IIS - Windows Server with ASP.NET Core Module
- etc.
Important: WebAuthn/Passkeys require HTTPS (except for
localhost)
Check the Configuration section for any new options and update your
appsettings*.jsonaccordingly.
It is recommended to check the latest docker-compose.yaml for any changes before updating.
Pull the latest image and recreate:
docker compose pull
docker compose up -d --force-recreate
Pull the latest changes and publish:
git pull
dotnet publish -c Release -o publish
publish/Application --environment Production| Technology | Purpose |
|---|---|
| .NET 10 | MVC framework |
| SQLite | File-based database |
| FIDO2 (WebAuthn) | Passkey authentication via Fido2NetLib + SimpleWebAuthn |
| JWT | Token-based authentication for client integration |
| In-Memory Session | Session management (non-distributed) |
Note: This project is designed as a lightweight, simple authentication server suitable for small to medium-scale deployments. If you need enterprise-level scalability, you can fork this project and extend it with:
- Distributed databases (PostgreSQL, MySQL, SQL Server)
- Redis or distributed cache for session management
- Advanced logging and monitoring solutions
If this project helps you, please consider giving it a Star ⭐️ on GitHub. This will encourage us to continue developing and maintaining this project.
This project is licensed under the MIT License - see the LICENSE file for details.


