Skip to content

Spec: Clarify auth responses in the REST spec #6251

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
danielcweeks merged 1 commit into from
Nov 27, 2022
Merged

Spec: Clarify auth responses in the REST spec #6251

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 9 additions & 2 deletions open-api/rest-catalog-open-api.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -506,10 +506,10 @@ paths:

The response contains both configuration and table metadata. The configuration, if non-empty is used
as additional configuration for the table that overrides catalog configuration. For example, this
configuration may change the FileIO implemented used for the table.
configuration may change the FileIO implementation to be used for the table.


The response also contains the table's full metadata.
The response also contains the table's full metadata, matching the table metadata JSON file.


The catalog configuration may contain credentials that should be used for subsequent requests for the
Expand Down Expand Up @@ -2385,6 +2385,13 @@ components:
securitySchemes:
OAuth2:
type: oauth2
description:
This scheme is used for OAuth2 authorization.


For unauthorized requests, services should return an appropriate 401 or
403 response. Implementations must not return altered success (200)
responses when a request is unauthenticated or unauthorized.
flows:
clientCredentials:
tokenUrl: /v1/oauth/tokens
Expand Down