WLP 6.9.22.7 asks to re-login
Author: Eugene
Creation Date: 12/27/2019 8:17 PM
profile picture

superticker

#1
There's a bug or something in WLP 6.9.22.7. It's asking me to re-login in the middle of the trading day. Previous versions never did that. Please fix that soon.

Also, when restarting WL during development, I don't want to have to re-login on each and every restart. It should remember my login from the session 10 minutes earlier and let me in automatically.

Also, try to setup the Install Shield script so you can install over the top of the existing WL installation like most updates work with Install Shield.

---
UPDATE: WLP 6.9.22.7 is asking me to re-login in the middle of the trading day for the second time. Is it going to do that every hour? Am I the only one with this problem? Is this a problem on the server side, or do I need to downgrade back to WLP 6.9.20.X to fix this?

It just asked me to re-login for the third time in the middle of the trading day. Looks like it's asking me again after 30 minutes. I'll call Fidelity and find out what the problem is. UPDATE: The best fix is to downgrade the WL client. Fidelity says the server side is okay.

I do have multiple Fidelity accounts. Does that make a difference? Would WL need to create separate authentication tokens for each Fidelity account I have independently?
profile picture

superticker

#2
QUOTE:
... WLP 6.9.22.7. It's asking me to re-login in the middle of the trading day.... I do have multiple Fidelity accounts. Does that make a difference?
I'm still getting re-login requests from WLP 6.9.22.7, but they aren't as frequent as initially. On the first day of using it, I got 4 re-login requests typically when switching accounts on the Account Balances window. On the second day of using it, I got 10 re-login requests prior to the market open; that's the period where I post all my stop/limit sell orders to the Orders window for all my different accounts. Lately, I've only gotten one or two re-login requests per trading day. Why this difference?

My question is, does this have something to do with all the server error 500s in the error logs, or is that something else? See screenshot below. I have a fast Internet connection, which is excellent.


Other than that, the WLP 6.9.22.7 version works pretty well.
profile picture

Glitch

#3
Hey Superticker, as you’ve noticed, Fidelity has made us adopt a new login mechanism. Unfortunately this means that saving the login info even for 10 minutes won’t be allowed due to their security protocols. I do believe I have the solution to the frequent logins though. It seems the back end times out the login after one hour without having made a certain back end call like a trade or account info request. I already have a fix that is working in development, it makes a behind the scenes request every 30 minutes which keeps the login fresh.
profile picture

superticker

#4
QUOTE:
It seems the back end times out the login after one hour without having made a certain back end call like a trade or account info request.
On the second day I was using WLP 6.9.22.7, I had 10 re-login requests before market open. During that time, I was creating stop/limit sell orders like crazy (like I do every trading day before the market opens), but they were being allocated to several different accounts. I'm wondering if using several different accounts makes a big difference?

What's weird is that re-login requests have been less frequent lately (just one or two), but maybe that's because my inter-account activity has been different. I do commonly trade between four different Fidelity accounts (although I have more accounts I never use with WL).

If you have a fix, that's great news. If not, and you can't reproduce this problem, I'm happy to install a beta WLP version that will write out a debug line to the error logger each time the re-login dialog comes up. I run WLP with error logging set to level=ERROR (hard error), so anything of that severity should be logged. I can then send you the log4net wlp.txt file at the end of several trading days. The error logging line might want to include [1] the last 3 digits of the account in question, and [2] the type of authentication token that expired and triggered the re-login.

Thanks for making WL a great program. It certainly ferrets out the trading opportunities.
profile picture

superticker

#5
I'm wondering why WLP 6.9.22.7 is asking me to re-login every 3- to 5-minutes this morning (before the US market opens)? In one case, I re-logged in, and as soon as I did, it asked me to re-login again. Is that because I need to do a re-login for each and every Fidelity account I have? That's crazy.

My point is that there's something wrong at the authentication server end that needs fixing. If you've re-logged in 5-minutes ago, the server shouldn't want a new re-login under any circumstances. You need to get Fidelity to fix their server side. Oops, I need to re-login in again; I have to go.
profile picture

superticker

#6
UPDATE: I tried turning on streaming updates for the Account Balances window, but that didn't generate enough activity to prevent the re-login requests from continually coming up. The bottom line is that one has to be posting orders throughout the day to prevent re-login requests. So if you're an intraday trader, you might be good. If you're an end-of-the-day trader, you're screwed with all the re-login requests for WLP 6.9.22.7.
profile picture

superticker

#7
This morning, before market opens, I'm having re-login dialog boxes queuing up such that when I re-login with the first box, another re-login box immediately comes up for WLP 6.9.22.7. What's going on? Yesterday, I didn't get any re-login boxes. Can someone please explain what the trick is to keeping the re-login boxes away? Thanks.

The re-logins are most frequent before market opens when the Quotes window isn't streaming new data. So somehow activity on both the Orders window and Quotes window are involved for all accounts one's trading against. (Activity on Fidelity accounts one's not trading against don't matter.) Oops, I got to re-login again.

---
Slightly off topic, but if Active Trader Pro employs the same login dialog as WLP, is it having the same re-login problems? If not, why not?
profile picture

Cone

#8
You'd think it wouldn't be such a challenge, would you?

From what we're told, the problem is still one of those cookies that needs to be kept alive in the background. It seems that WLPro is having trouble doing that (or isn't doing it with the right set of cookies still). The only hunch we have for a work-around right now that if you refresh the Accounts page or send in an order, at least once every hour, that will be enough to prevent those force login boxes. Let us know if that helps.
profile picture

superticker

#9
QUOTE:
You'd think it wouldn't be such a challenge,...?
Ha, ha; you must be psychic--you read my mind. I have two questions:

1) The re-login events occur even on weekends (not as frequent, though). So am I suppose to be making trades on weekends to avoid these re-logins? And would switching accounts on the Account Balances window really help on weekends? My general thinking is that there's something wrong on the Fidelity authentication server side if it requires active trading activity on weekends to stay logged in. Thoughts? (Perhaps I'm missing something.)

2) Does ATP have the same re-login problems? If not, why not? Is it somehow doing something in the background that keeps the re-logins away? If so, how can I duplicate that activity on WLP?

As I suggested in Post# 4, I'm happy to beta test a WL solution that would write out to the error log the token type that needs re-authentication with the account it applies to each time the re-login dialog box comes up so you can nail which token(s) is(are) causing the problem. I also appreciate this whole refresh-the-token approach is "unnecessarily" if the Post# 3 keep-alive fix is implemented. There's no need to refresh the tokens if they never expire in the first place.
profile picture

ClockDrift

#10
For what it's worth, I too am getting prompted for re-logging in during the day which defeats the auto-trading feature (version 6.9.22.7). It's disappointing because I spent a lot of time developing a strategy specifically for auto-trading, I hope all that effort wasn't wasted. I am taking the work-around suggested above and clicking on 'Account Update' at least every hour, but it's becoming a real drag and not very practical. Is this the best work around? I suppose I could develop a strategy that buys one share of stock every 15 minutes, and then sells it all at the end of the week, but that has serious drawbacks too. Is there any ETA for a fix?
profile picture

superticker

#11
This morning, I got re-login boxes every 30-seconds. I must have re-logged in 70 times. At one point I quite WL and restarted it. But after logging in, I got another re-login box within the next minute. What's going on here?

What's weird is that for many days this isn't a serious problem. But on some days (like today) the re-login's are continuous. Why is that?

I called Fidelity, and they don't seem to know much about it. Why not? He suggested reinstalling the program. Would that really help?

Anyway, when will this problem be fixed?
profile picture

Cone

#12
It could be a temporary condition, but whenever you have trouble with login, shutdown WLP and restart. And, always start fresh shortly before the market open. Don't waste time reinstalling.
profile picture

superticker

#13
Thanks for your feedback and concern; it's greatly appreciated. Funny thing, but this is never a problem at night. And when it is a problem, it's typically just before and after the market opens. But on really high market volume days, it can be a problem throughout the day.

I have not checked the error logs for high volume days to confirm this, but I'm wondering if it's tied to server 500 error that "might" occur more on high volume days; that's a theory. If it would help you troubleshoot it, I can check the error logs (Gee, I can send you my entire *.log file.) so you can try to correlate high-volume days with the server 500 errors, which are timestamped.

My guess is you already know what the problem is so you don't need my error logs. But if you want to correlate high-volume days with server 500 errors, let me know and I'll create a support ticket and send them to you. I run my logs at LEVEL=ERR so the salient 500 errors should all be recorded there.
This website uses cookies to improve your experience. We'll assume you're ok with that, but you can opt-out if you wish (Read more).