BobSong-dev opened a new issue, #7953: URL: https://github.com/apache/shenyu/issues/7953
## Background P1-09 in the mentor-approved OSPP plan; parent #7949. Production MCP services may require controlled HTTPS hostnames and operational credential rotation, beyond fixed-IP targets. ## Existing capabilities and reuse At master `87c22dde7`, RemoteTransportPolicy explicitly rejects DNS-based targets and uses direct connections; RemoteServerBinding and credential resolvers bind service credentials to trusted endpoints. Reuse these boundaries and configuration synchronization. Do not forward caller credentials or diagnostic subjects to remote servers. Related #6471 concerns separate AI Proxy client credential-cache isolation, not this MCP transport extension. ## Implementation scope - Support approved HTTPS DNS/service-discovery targets with one coherent policy for resolution, allowed addresses, actual connection destination, TLS hostname/SNI and certificate validation. Enforce the policy at connection time, not merely URL parsing. - Bound DNS resolution/re-resolution, connection attempts and discovery results; defend against DNS rebinding and unauthorized address changes, including pooled-connection behavior. - Preserve independent target-bound credentials; define versioned rotation and emergency revocation semantics for new and in-flight requests, cached bindings and pooled clients. Never publish secrets in config diagnostics or metrics. - Keep fixed-IP compatibility and redirects disabled. Document trusted configuration, rejection semantics and deployment requirements. ## Non-goals Arbitrary URL fetching, permissive TLS/trust-all, delegated OAuth, unrestricted enterprise proxies, IPv6 expansion without an actual requirement, or a new service-discovery platform. ## Acceptance criteria - [ ] DNS allowlist, connected address and TLS/SNI validation agree; rejected/changed destinations cannot bypass policy via retries or connection reuse. - [ ] Invalid/untrusted certificates and hostname mismatches fail closed. - [ ] Rotation/revocation has documented, tested new/in-flight semantics without cross-target secret reuse. - [ ] Fixed-IP paths remain compatible; unauthorized configuration is rejected in Admin/runtime. ## Tests Controlled DNS/rebinding fixture and real TLS MCP endpoints; SAN/hostname/certificate failures; pool reuse and address-change races; credential rotation/revocation with concurrent calls; cancellation/timeouts and secret-redaction regression. Use test CA configuration only in fixtures, never weaken production validation. ## Dependencies P0-01/P0-02 and P1-07; coordinate credential refresh with P1-08. Resolve the concrete approved domain/discovery deployment policy during design before broadening outbound access. -- 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]
