Maybe you get more responses from IBC support group. Insync is a perfect tool but for connection with IBKR is in my view fully dependent on IBC. I think also that insync group may be is not the best choice for solving the IBKR connection issues.
#INSYNC 2 LOGIN PASSWORD#
Another advantage: Because the data was backed up from the employee’s laptop, it’s accessible to anyone in the company who needs it. Leave the Password field blank if you are using Single Sign-On. 2 factor authentication now can use more ways including IBKR mobile, which is easier for automation. The functionality that permits Druva inSync to wipe the corporate data off a lost or stolen laptop or iPad also lets IT wipe the corporate data (but not the personal data) off the employee’s BYOD devices. So I think in general for a reliable automatic trading your programs have to monitor the connection with gateway/TWS as well as for various reasons occured to be able to recover its processes tied to IB connection as well as to reestablish the connection with IBKR servers. It is not only 2 factor sign in event your program has to solve in real life automatic trading, there are much more events including many reasons why you lose or have to reestablih the connection with IBKR servers. You will be prompted to confirm this action.
Go to the License tab on the top row and click Remove Account. But in my opinion it is very risky to disable 2 factor authentication just only for easier sign in. Click your account on the top (circular avatar) and hover over and click the Account preferences icon on the bottom left of your app. I am not sufficiently experienced to give you some advice. It is very important topic in my opinion.
Hi Refael, surprised you have not received any substatial advice yet from anybody.
0 kommentar(er)
