yuqi1129 opened a new issue, #14871:
URL: https://github.com/apache/gravitino/issues/14871

   ### What would you like to be improved?
   
   The MCP server can serve its endpoint over HTTPS (`--tls-cert`/`--tls-key`) 
and can call an `https://` `--gravitino-uri`, but:
   
   - The docs do not say how to trust a Gravitino certificate signed by a 
private CA. The server uses httpx, which verifies against its bundled public 
roots; `SSL_CERT_FILE` works but replaces those roots rather than adding to 
them, so a file holding only the private CA breaks connections to servers with 
public certificates, such as an identity provider's token endpoint.
   - No test makes a real TLS connection. `test_transport_tls.py` only checks 
the arguments passed to uvicorn, so a regression in how the listener's 
certificate reaches uvicorn, or in outbound trust, would go unnoticed.
   
   ### How should we improve?
   
   - Document private-CA trust for `--gravitino-uri`: build a bundle with the 
public roots plus the CA, set `SSL_CERT_FILE`, note that it applies to every 
outbound HTTPS call including the OAuth token endpoint, and that certificates 
and the bundle are read at startup.
   - Add end-to-end tests with throwaway certificates from one private CA: a 
Gravitino stub over HTTPS (trusted bundle succeeds, untrusted fails with 
`CERTIFICATE_VERIFY_FAILED`) and the MCP endpoint launched with 
`--tls-cert`/`--tls-key` (TLS with the CA succeeds; default roots and plain 
HTTP fail).
   


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

Reply via email to