{"ref":"content:using-the-tcp-protocol-for-node-js-cloud-applications","page":"/content/using-the-tcp-protocol-for-node-js-cloud-applications","json":"/content/using-the-tcp-protocol-for-node-js-cloud-applications.json","generated":"2026-11-09","drafted_with_ai":true,"entity":{"id":"using-the-tcp-protocol-for-node-js-cloud-applications","title":"Using the TCP Protocol for Node.js Cloud Applications","url":"https://community.sap.com/t5/technology-blog-posts-by-members/using-the-tcp-protocol-for-node-js-cloud-applications/ba-p/13537554","content_type":"blog","published_on":"source:sap-community","explains":["artifact:btp-connectivity"],"summary":"A Node.js SOCKS5 client module, published in full, for reaching an on-premise TCP service — the walkthrough uses LDAP — through the [SAP Connectivity service](artifact:btp-connectivity)'s proxy on BTP Cloud Foundry, written to complement SAP's own Java example for the same proxy. It gets the service token through the connectivity service binding's client_credentials grant and implements the proxy's custom JWT authentication handshake byte by byte, rather than going through a named destination.","author":"laszlo_kajan2","published":"2022-02-21","provenance":{"discovered_via":[{"source":"source:sap-community","channel":"connectivity-tag"}],"first_seen":"2026-11-08"},"drafted_with_ai":true},"readings":{"liveness":[{"label":"Checked against the source","tier":"unknown","evidence":"nobody has checked it"},{"label":"Source reachable","tier":"unknown","evidence":"not crawled"},{"label":"Age","tier":"poor","evidence":"published 57 months ago"}],"compatibility":[{"label":"Version","tier":"unknown","evidence":"no version declared"},{"label":"Moved since?","tier":"good","evidence":"no recorded change after 2022-02-21"},{"label":"Findings","tier":"good","evidence":"none flagged"}],"reach":[{"value":null,"unit":"views"},{"value":null,"unit":"comments"},{"value":null,"unit":"likes"}]},"signals":null,"series":null,"edges":{"authors":[]}}