Skip to content

refactor: retain typed control configuration - #37

Merged
0xcadams merged 1 commit into
0xcadams/type-authorization-scopefrom
0xcadams/type-control-config
Oct 1, 2026
Merged

0xcadams merged 1 commit into
0xcadams/type-authorization-scopefrom
0xcadams/type-control-config

Conversation

@0xcadams

@0xcadams 0xcadams commented Oct 1, 2026 •

Copy link
Copy Markdown
Member

What

Carry the existing tnld process role and OIDC login-flow types through the control API configuration handoff.

Why

Server configuration validates these choices, but runtime converted them to generic strings before handing them to control. Keeping their types across that boundary makes the handoff and subsequent discovery response clearer.

Changes

  • Use tnldconfig role and OIDC flow types in controlapi.Config and pass them through from runtime.
  • Convert to the generated API enum when building discovery responses, with coverage for both supported OIDC login flows.

@0xcadams
0xcadams force-pushed the 0xcadams/type-control-config branch from 0fe7465 to 11014f1 Compare October 1, 2026 06:01
@0xcadams
0xcadams changed the base branch from main to 0xcadams/type-authorization-scope October 1, 2026 06:03
@0xcadams
0xcadams added this pull request to stack #43 October 1, 2026 06:03
@0xcadams
0xcadams force-pushed the 0xcadams/type-control-config branch from 11014f1 to 0036b8a Compare October 1, 2026 06:30
@0xcadams
0xcadams merged commit c6a7d96 into main Oct 1, 2026
23 checks passed
@0xcadams
0xcadams deleted the 0xcadams/type-control-config branch October 1, 2026 06:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant