1:30pm Pacific will be great. To run the session can you run the app that downloads from the following link at the meeting time?
https://get.teamviewer.com/tikhelp We can try it with a fresh new data file if you like, but if that works then we should also make sure it works with your main data file as well.
After struggling with my Costco Citi VISA all year, I finally nailed the issue. Sadly, it really appears like an issue that IK should have found. I wasn't getting 2000 errors but rather cryptic 13504 errors (with no useful information). I followed hleofxquotes's brilliant debugging steps using the curl and the desktop and it was completely obvious: At some point 1Password had generated a sweet, long, random password for Citibank and it contained a '<' character. IK was sending that character through as part of the password without escaping it and Citi was choking on it. Switching my password to a still very long, but special character-less password fixed everything.
And Infinite Kind, you really need to properly escape the data you are passing. It seems like it could have the potential to allow some code injection.
on 24 Nov, 2019 10:13 PM
>>> And Infinite Kind, you really need to properly escape the data you
are passing. It seems like it could have the potential to allow some
Not escaping the special character and sending an invalid byte array
would be an IK _bug_. If it resulted in a _code injection attack_ that
would be the fault of Citi bank but sounds like Citi bank did proper
bounds checking of the input string and rejected the invalid character
as they should have.
BTW: Thanks for all the diligence and effort chasing this down.
Apologies to IK, but I obviously didn't have enough information to make my claims as to whose fault it was. It could be a problem with the data sent by IK, or it could be a problem with the way Citi handles the incoming data. Either way, the error message "Failure" doesn't really lend itself to correction on my side and after six months of struggling, I was just relieved to have things working again.
In any event, I was able to resolve the problem by switching to a password with no special characters. My old password had a '<' which may have been the culprit. Fortunately, Citi accepts passwords of up to 50 characters, so I can still trust my random password to be secure.