Yukang-Lian opened a new pull request, #64016:
URL: https://github.com/apache/doris/pull/64016

   ### What problem does this PR solve?
   
   Issue Number: None
   
   Related PR: #63145
   
   Problem Summary: This re-submits the OSS mTLS framework work from #63145 
under my account and rebases it onto the latest apache/doris master. The change 
ports the public mTLS scaffolding, configuration, protocol startup split, 
certificate-auth contracts, and TLS validation tests while excluding enterprise 
module directories.
   
   After the rebase, the previous FE UT failures were fixed: the ALTER/CREATE 
USER TLS unit tests now use Mockito static mocking instead of external JMockit 
parameter injection, and the MetaServiceProxy success-path test now stubs the 
mock client as using the latest channel configuration so the proxy does not 
replace it before executing the request.
   
   ### Release note
   
   Add OSS mTLS framework scaffolding and TLS validation coverage.
   
   ### Check List (For Author)
   
   - Test: Unit Test
       - ./run-fe-ut.sh --run 
org.apache.doris.analysis.AlterUserStmtTest,org.apache.doris.analysis.CreateUserStmtTest,org.apache.doris.cloud.rpc.MetaServiceProxyTest
       - ./run-fe-ut.sh --run 
org.apache.doris.analysis.AlterUserStmtTest,org.apache.doris.analysis.CreateUserStmtTest,org.apache.doris.analysis.TlsOptionsTest,org.apache.doris.auth.certificate.SanEntryCodecTest,org.apache.doris.cloud.rpc.MetaServiceProxyTest
       - ./build.sh --fe
       - git diff --check
   - Behavior changed: Yes. Adds OSS TLS framework scaffolding and related 
validation tests.
   - Does this need documentation: No


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