Commit74161dd

committed

fix: support path parameters in OAuth2 metadata endpoints

Change-Id: Ic28d30af39fcb3c8eea40607e0241c5aa096cc80Signed-off-by: Thomas Kosiewski <tk@coder.com>

1 parent21402c7 commit74161ddCopy full SHA for 74161dd

File tree

-2

lines changed

-2

lines changed

Lines changed: 2 additions & 2 deletions

Original file line number	Diff line number	Diff line change
`@@ -948,9 +948,9 @@ func New(options Options) API {`
`948`	`948`	`}`
`949`	`949`
`950`	`950`	`// OAuth2 metadata endpoint for RFC 8414 discovery`
`951`		`-r.Get("/.well-known/oauth-authorization-server",api.oauth2AuthorizationServerMetadata())`
	`951`	`+r.Get("/.well-known/oauth-authorization-server*",api.oauth2AuthorizationServerMetadata())`
`952`	`952`	`// OAuth2 protected resource metadata endpoint for RFC 9728 discovery`
`953`		`-r.Get("/.well-known/oauth-protected-resource",api.oauth2ProtectedResourceMetadata())`
	`953`	`+r.Get("/.well-known/oauth-protected-resource*",api.oauth2ProtectedResourceMetadata())`
`954`	`954`
`955`	`955`	`// OAuth2 linking routes do not make sense under the /api/v2 path. These are`
`956`	`956`	`// for an external application to use Coder as an OAuth2 provider, not for`

Comments

(0)