Skip to content

Add clientId to openIdConnect schemes - #50

Open
cayetanobv wants to merge 1 commit into
stac-extensions:mainfrom
cayetanobv:openid-connect-client-id
Open

cayetanobv wants to merge 1 commit into
stac-extensions:mainfrom
cayetanobv:openid-connect-client-id

Conversation

@cayetanobv

Copy link
Copy Markdown
Contributor

Closes #49.

Adds an optional clientId field to openIdConnect schemes: the public OAuth 2.0 client ID a client signs in with at the provider. It's optional, so existing documents stay valid.

  • README: new row in the Authentication Scheme Object table
  • JSON schema: clientId (string) in the openIdConnect branch
  • collection-token-exchange.json example and CHANGELOG updated

@m-mohr

m-mohr commented Nov 15, 2026

Copy link
Copy Markdown
Contributor

I don't think a plain clientId works in practice, especially for Authorization Code + PKCE. The client ID only works with the redirect URIs (and, for browsers, the CORS origins) registered for it, so clients the provider doesn't already know would still be rejected. They also can't detect the failure, because the provider won't redirect back on a mismatch (RFC 6749 §4.1.2.1). A published client ID only works generically for the Device Code flow and for native apps using loopback redirects.

Thus, we have solved it differently in openEO's default_clients for example, so clients can check up front whether they can use it:

"clients": [{
  "clientId": "abc123",
  "grantTypes": ["authorization_code+pkce", "urn:ietf:params:oauth:grant-type:device_code"],
  "redirectUrls": ["https://example.com/browser/"]
}]

Generally, OIDC without secret is not that generic as we'd like it for good reasons (safety) and a solution should work more generically, not just for specific clients. Otherwise the proposal doesn't really solve it's purpose and can just be added to the known clients anyway.

This branch has not been deployed

No deployments
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.

Add clientId to openIdConnect schemes

2 participants