Skip to content

Split MicroZen.OAuth2 into MicroZen.Core + per-provider packages #69

Open

Description

@brinehart

Today all provider code ships in a single MicroZen.OAuth2 package (tracked tech debt). Target:

  • MicroZen.Core — shared provider-independent code (state, config, authority gRPC client, grant-type defs, JWT plumbing).
  • MicroZen.Auth.<Provider> — one package per provider (Cognito, Supabase, Entra, Auth0, Google).

Done when: core is extracted, Cognito is moved to MicroZen.Auth.Cognito, and consumers import only the provider they need. This is the prerequisite for the provider rollout issues.

See steering .kiro/steering/ecosystem.md (documented in PR #62). section 3.

Metadata

Metadata

Assignees

No one assigned

    Labels

    .NETPull requests that update .NET codeShould FixRisky code without a test, real slowness, duplication, or code that should not existenhancementNew feature or request

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions