fix: ensure openapi spec demonstrates auth when cql2 filters apply#135
Merged
fix: ensure openapi spec demonstrates auth when cql2 filters apply#135
Conversation
alukach
pushed a commit
that referenced
this pull request
Feb 21, 2026
🤖 I have created a release *beep* *boop* --- ## [1.0.1](v1.0.0...v1.0.1) (2026-02-21) ### Bug Fixes * ensure openapi spec demonstrates auth when cql2 filters apply ([#135](#135)) ([7310cee](7310cee)) * support filtering bulk item creation ([2c4a791](2c4a791)) ### Documentation * **record-level-auth:** add filter factory guidance ([47c4e68](47c4e68)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: ds-release-bot[bot] <116609932+ds-release-bot[bot]@users.noreply.github.com>
This was referenced Mar 7, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Currently, the Swagger UI won't send auth credentials to endpoints if those endpoints are not marked as having a
securityscheme. While an endpoint may be public, the auth proxy might make use of those auth credentials to generate & apply CQL2 filters for row-level auth. As such, we should annotate an auth requirement to any endpoint that has CQL2 filters associated with it. It's important to note that these annotations do not actually denote an enforcement of auth, Swagger UI will still permit unauthenticated access. These annotations merely inform the Swagger UI client that auth credentials should be provided if possible.