Connect for Swift 1.2

Apply the Swift 6.3 baseline first. These rules cover Connect-Swift 1.2 client applications, generated clients, interceptors, and the optional ConnectNIO transport, and were checked against 1.2.3. Require the remote service to enforce authentication and object- and tenant-level authorization; generated clients and client-side validation cannot enforce server policy.

Version and transport configuration

• Build with Swift 6.3 and verify the resolved dependencies' toolchain requirements. Connect declares Swift tools 5.6 and Swift 5/6 language modes, but its dependency minimums require newer tools. Its declared platform floors are iOS 12, macOS 10.15, tvOS 13, and watchOS 6; the async interfaces require iOS 13 or later.
• Set ProtocolClientConfig.networkProtocol and codec deliberately; their defaults are .connect and JSONCodec(). Use URLSessionHTTPClient for Connect or gRPC-Web and ConnectNIO.NIOHTTPClient for .grpc, which requires HTTP trailers unavailable through the URLSession transport.
• For ConnectNIO builds, check swift-nio, swift-nio-http2, and swift-nio-ssl separately from Connect: Connect 1.2.3's declared lower bounds admit releases that predate published fixes, and vulnerability scanners miss some SwiftNIO advisories. Before each release, compare the versions in Package.resolved with the fixed releases listed on each project's GitHub security advisory page, move to them with swift package update <name>, confirm their Swift tools requirement fits your toolchain, and check each advisory's applicability to the modules and custom APIs