Skip to main content
net10.0

Test identity provider for Koan Web Auth: local login UI, token issuance for demos, and development-only wiring.

Published
Sep 9, 2026
1mo ago
Total Downloads
4.0K
4,048

Install

dotnet add package Sylin.Koan.Web.Auth.Connector.Test --version 1.0.47
ProductVersions
.NET
net10.0

README

Sylin.Koan.Web.Auth.Connector.Test

A self-hosted OAuth2/OIDC simulator for meaningful local and integration testing. Reference it and AddKoan() makes two automatic providers available in Development: test and test-oidc.

dotnet add package Sylin.Koan.Web.Auth.Connector.Test

Start the maintained OIDC flow at:

GET /auth/test-oidc/challenge?return=/

The local login page lets a developer choose a subject, roles, permissions, and custom claims. The resulting cookie travels through the same Web Auth scheme, callback, claim mapping, external-identity link, and lifecycle pipeline used by real providers.

Useful surfaces

  • login UI: /.testoauth/login.html;
  • OIDC discovery: /.testoauth/.well-known/openid-configuration;
  • OAuth2 authorize/token/userinfo: /.testoauth/authorize, /token, /userinfo;
  • JWKS: /.testoauth/jwks.

Use prompt=login or prompt=select_account to force persona selection. Application logout also clears the local persona cookie.

Guarantees and boundaries

  • Automatic only when TestProviderOptions.IsActive is true: Development by default, or explicit enablement outside Development.
  • Stable attribute-routed protocol endpoints; no configurable route base or startup-order dependency.
  • Container and reverse-proxy flows preserve the browser-visible issuer while discovery, token, userinfo, and JWKS calls use the application's internal bound address automatically; no Docker hostname setting is required.
  • The provider is a protocol simulator, not a security or production identity system. Do not enable it in production.
  • Personas persisted in browser LocalStorage are developer convenience, not durable identity data.

See TECHNICAL.md.

Changes from Previous Version

No structural changes between v1.0.43 and v1.0.47.

Adoption Assessment

Assess this package against its supported frameworks, license, maintenance signals and dependency graph before making it a project standard.

Compatibility metadata lists 1 target framework; confirm the exact target used by your application.The published metadata declares 25 direct dependency entries across framework groups. Inspect the resolved dependency graph for your target framework.

Related Guides & Workflows

Learn how to evaluate, integrate, or audit this package in your .NET project.