Our CP Gateway tool is essentially an HTTP web server acting as a reverse proxy, forwarding your requests to IBKR. It ships with a stock, placeholder certificate that is expired. The CP Gateway is meant to be deployed locally, on the same device or local network as the request originator. You may substitute a self- or officially-signed certificate if you choose.
Why is the certificate included with the CP Gateway tool invalid?
Powered by IBot
TWS/IB Gateway and their interaction with proxy servers
Can I automate the Web API authentication process?
Do I need to use two-factor authentication (2FA) when authenticating in the Web API?
Can I make requests to IBKR without running the local CP Gateway tool?