yuqi1129 opened a new pull request, #12954:
URL: https://github.com/apache/gravitino/pull/12954
### What changes were proposed in this pull request?
Document auxiliary and standalone authentication, service identity fallback,
operation privileges,
listing filters, concealed objects, and the boundary between metadata and
storage access.
Extend HTTP integration coverage for authentication errors, active roles,
authorized fallback,
health checks, and standalone backend identity. Add a reproducible test
command to the integration guide.
### Why are the changes needed?
Users need a complete description of Lance REST metadata authorization and
tests that verify
identity and privileges across the HTTP request chain.
Fix: #12574
### Does this PR introduce _any_ user-facing change?
Documentation and integration tests only; no API or configuration changes.
### How was this patch tested?
Passed 113 tests (22 HTTP integration tests plus 91 unit tests), with no
failures or skips.
```shell
./gradlew :lance:lance-rest-server:spotlessApply
:lance:lance-rest-server:test \
--tests '*LanceNamespaceAuthorizationIT' --tests
'*LanceTableAuthorizationIT' \
--tests '*LanceRESTServiceAuthIT' --tests
'org.apache.gravitino.lance.service.*' \
--tests 'org.apache.gravitino.lance.common.*' -PskipDockerTests=true
```
Locally used a writable temporary Gradle cache, offline dependency
resolution, and
`-x :lance:lance-rest-server:prepareLanceSparkBundle_0_4_0` to reuse the
already present
Spark bundle (these tests do not run Spark). Module Spotless checks, `git
diff --check`,
and local documentation links passed. Full-repository `spotlessApply`
encountered an
unrelated Python/uv cache permission error.
Authentication coverage uses simple authentication and local storage, not
external
OAuth2/Kerberos providers or object-store policies.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
