Skip to content

Add scope support to OpenIdConnectAuth#11153

Open
tellnes wants to merge 1 commit into
microsoft:mainfrom
tellnes:feature/openidconnect-scopes
Open

Add scope support to OpenIdConnectAuth#11153
tellnes wants to merge 1 commit into
microsoft:mainfrom
tellnes:feature/openidconnect-scopes

Conversation

@tellnes

@tellnes tellnes commented Jul 2, 2026

Copy link
Copy Markdown
Contributor

The model now accepts an optional Scopes template parameter so operations can declare required scopes. The OpenAPI3 emitter emits those scopes on each operation's security requirement while the scheme object itself remains unchanged. Existing usages without scopes are unaffected.

The model now accepts an optional `Scopes` template parameter so
operations can declare required scopes. The OpenAPI3 emitter emits
those scopes on each operation's security requirement while the
scheme object itself remains unchanged. Existing usages without
scopes are unaffected.
@tellnes tellnes force-pushed the feature/openidconnect-scopes branch from 9826a58 to 3fd3841 Compare July 2, 2026 16:37
@pkg-pr-new

pkg-pr-new Bot commented Jul 2, 2026

Copy link
Copy Markdown

Open in StackBlitz

npm i https://pkg.pr.new/@typespec/http@11153
npm i https://pkg.pr.new/@typespec/openapi3@11153

commit: 3fd3841

@github-actions

github-actions Bot commented Jul 2, 2026

Copy link
Copy Markdown
Contributor

All changed packages have been documented.

  • @typespec/http
  • @typespec/openapi3
Show changes

@typespec/http - feature ✏️

Add scope support to OpenIdConnectAuth. The model now accepts an optional Scopes template parameter (OpenIdConnectAuth<ConnectUrl, Scopes>) and the OpenAPI3 emitter emits those scopes on each operation's openIdConnect security requirement. The scheme object itself remains unchanged (scopes are discovered via the openIdConnectUrl). Existing OpenIdConnectAuth<Url> usages are unaffected.

@typespec/openapi3 - feature ✏️

Add scope support to OpenIdConnectAuth. The model now accepts an optional Scopes template parameter (OpenIdConnectAuth<ConnectUrl, Scopes>) and the OpenAPI3 emitter emits those scopes on each operation's openIdConnect security requirement. The scheme object itself remains unchanged (scopes are discovered via the openIdConnectUrl). Existing OpenIdConnectAuth<Url> usages are unaffected.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

emitter:openapi3 Issues for @typespec/openapi3 emitter lib:http meta:website TypeSpec.io updates

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant