viirya opened a new pull request, #5:
URL: https://github.com/apache/spark-connect-gateway/pull/5

   ### What changes were proposed in this pull request?
   
   Part of importing the Spark Connect Gateway reference implementation into
   `apache/spark-connect-gateway` as a series of small, bottom-up PRs (tracked 
in
   the do-not-merge reference PR #1).
   
   This adds the `scg-auth` crate — the authentication layer for the gateway. It
   defines the `Authenticator` abstraction and the verified `Identity` attached 
to
   an authenticated request, a tonic interceptor that runs an authenticator and
   stamps the identity onto the request, and several authenticator 
implementations:
   
   - `AnonymousAuthenticator` — used when auth is explicitly disabled
   - `StaticTokenAuthenticator` — a Bearer-token allowlist
   - `JwtAuthenticator` — verifies a signed JWT against a local key
   - `OidcAuthenticator` — verifies JWTs against a remote JWKS endpoint
   
   `scg-auth` is a leaf crate (no internal dependencies), so it compiles and 
tests
   on its own (30 unit tests). It is appended to the workspace `members` list, 
and
   is a prerequisite for the `tenant` and `proxy` crates that arrive in later 
PRs.
   
   ### Why are the changes needed?
   
   Implements the reference gateway from the approved SPIP (SPARK-58455), 
imported
   one reviewable piece at a time.
   
   ### Does this PR introduce _any_ user-facing change?
   
   No.
   
   ### How was this patch tested?
   
   `cargo fmt --all --check`, `cargo clippy --workspace --all-targets -- -D 
warnings`,
   `cargo build --workspace`, and `cargo test --workspace` all pass locally
   (scg-auth has 30 unit tests).
   
   ### Was this patch authored or co-authored using generative AI tooling?
   
   Yes, co-authored with Claude Code.
   


-- 
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]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to