To comply with exchange regulations we will be disabling simultaneous sessions across Kite apps with immediate effect. For example, if you log in to Kite Web and then later log in to Kite Android or iOS then Kite Web session will expire. At the same time, only one session will be valid.
1. I log in to kite connect at 9 AM having two instances running at the same time with same user id. 2. then I log in to Kite web at 10 AM. Will any of the session be logged out?
@tonystark Just to be clear, if I've logged into kiteconnect API and use it to query through the whole day from the program, then I log in through my android phone, it won't log out the kiteconnect API. Correct?
@tonystark I am using one access token to perform on one algo, another access token to perform 2nd algo and 3 access token to perform some backtest. Am I impacted by this change?
@sujith I understand what's the solution. My question was more to validate if this was due to the recent changes of disabling of simultaneous sessions as per exchange regulations. I had not noticed this behaviour in my last 2 years of using Kite connect.
Is this still a problem today? Because, I face no problems whatsoever while I'm logged in simultaneously in Kite Web, Kite Connect, and the Android Kite app.
This is not working for me @vijoeyz. I have my python client app registered as Client Connect App as well. When ever I login using the client app, my web session is logged out. I am using KiteConnect for python to generate kite session and perform trading. Can you help?
I am getting logged out many times from Kite Web even when I follow this workaround. Praveen from your customer care says that Kite Web and Kite API cannot be used at the same time. How will a user use your API is such a constraint?
I have been successfully using both Kite Web, Kite Connect, and Kite Android app simultaneously. There are two methods:
In the first method, login into Kite Web first, and in the same web browser perform the Kite Connect login flow. These both will use a single (the same) authentication token.
The second method is the opposite of the first: i.e., complete the Kite Connect login flow, and then the Kite Web. However, there is a catch in this method: you must tick the box "Login to Kite Web also?" every time! If you do not do this and log in to Kite Web separately (after Kite Connect login), that will generate a new token for Kite Web, which will invalidate Kite Connect's token!
Therefore, I follow the first method. It seems the Kite app uses a different method and does not affect or depend on Kite Web and Connect's shared token.
I have been using both too, but sometimes when I open multiple kite web tabs at same time, all my kite web sessions log out. When I raised this complaint, Zerodha customer care told me that we are not allowed to use web and API at the same time
If you follow @vijoeyz way of logging in, then there won't be any issue. Saving a bookmark is just copying a url, it doesn't save cookies and all. If session exists then you will land on that url or else you will land on login screen.
It is not working Sujith, when I open multiple bookmarked tabs at once, it logs me out of all the sessions on kite web! This happens only on few days. Srini said he will look into this.
2. then I log in to Kite web at 10 AM.
Will any of the session be logged out?
@krtrader @RishiS Like I said in the post: If you experience any issue, let us know.
Yes, this was done to align with regulator's interests.
I am using KiteConnect for python to generate kite session and perform trading.
Can you help?
In the first method, login into Kite Web first, and in the same web browser perform the Kite Connect login flow. These both will use a single (the same) authentication token.
The second method is the opposite of the first: i.e., complete the Kite Connect login flow, and then the Kite Web. However, there is a catch in this method: you must tick the box "Login to Kite Web also?" every time! If you do not do this and log in to Kite Web separately (after Kite Connect login), that will generate a new token for Kite Web, which will invalidate Kite Connect's token!
Therefore, I follow the first method. It seems the Kite app uses a different method and does not affect or depend on Kite Web and Connect's shared token.
Zerodha's support never satisfied me. Usually, they only give standard copy-paste answers, but never specific answers. Don't depend on them.
True, Zerodha Customer care quality has been degrading substantially over time, Nithin focusing more on money now!
It is an issue at zerodha's end.
Saving a bookmark is just copying a url, it doesn't save cookies and all. If session exists then you will land on that url or else you will land on login screen.