Re: [GNC] AqBanking help for Citi CC (cont'd again)

2019-10-28 Thread David Reiser via gnucash-user
> On Oct 22, 2019, at 12:33 AM, xngin  wrote:
> 
> Greetings everyone,
> 
> I'm happy to report a working Citi CC OFX Direct Connect through AqBanking.
> It took quite a bit of tinkering to figure out. For a while I was stuck on
> the fact that  had to be a UUID4, which AqBanking cannot produce,
> but it seems that Citi changed something and now it works as is.
> 
> It may be helpful for me to mention that I first discovered the correct OFX
> request, and then got AqBanking working. A working OFX request is included
> at the bottom of this message. Unfortunately, it has been a while since I
> stumbled upon it and I vaguely recall that the request alone was not enough.
> I am speculating now, but I think I had to enable that 10 minute window
> mentioned in the thread and during it send a simple signon request (with no
> transaction/statement request field). Only after it returned a success was I
> able to request data.
> 
> In terms of submitting the request, I have a few working options: 
> 1) a POST request with the following headers 'Content-Type':
> "application/x-ofx", 'User-Agent':"InetClntApp/3.0", "Accept":"*/*"
> 2) a call to ofxget (part of ofxtools) with the following configuration file
> (~/.config/ofxtools/ofxget.cfg):
> 
> [citi]
> version = 103
> appver = 2500
> creditcard = # 16 digit credit card number # 
> org = Citigroup
> fid = 24909
> user = #username#
> url = https://mobilesoa.citi.com/CitiOFXInterface
> pretty = true
> unclosedelements = true
> 
> 3) AqBanking v5.7.8 with the following configuration file:
> ~/.aqbanking/settings/users/uid0001.conf
> 
> int  uniqueId="58"
> char backendName="aqofxconnect"
> char userName="username"
> char userId="username "
> char customerId="username "
> char country="us"
> char bankCode="00"
> int  lastSessionId="0"
> 
> data {
>  backend {
>char bankName="Citi Credit Card"
>char org="Citigroup"
>char fid="24909"
>char serverAddr="https%3A%2F%2Fmobilesoa.citi.com%2FCitiOFXInterface"
>char appId="QWIN"
>char appVer="2500"
>char headerVer="103"
>char clientUid="a fixed UUID4 string"
>int  httpVMajor="0"
>int  httpVMinor="0"
>  } #backend
> } #data
> 
> 
> 
> Finally, here is the working OFX request. If you find this information
> useful, please consider adding it to the GnuCash wiki.
> 
> OFXHEADER:100
> DATA:OFXSGML
> VERSION:103
> SECURITY:NONE
> ENCODING:USASCII
> CHARSET:1252
> COMPRESSION:NONE
> OLDFILEUID:NONE
> NEWFILEUID:#random uuid4 or just some random large integer, like
> 20180912052115#
> 
> 
>
>
>20191020111537.000
>#username#
>#passsword#
>ENG
>Citigroup24909
>QWIN
>2500
>#uuid4, i keep it fixed between sessions, but don't
> recall setting it#
>
>
>
>
>20191021211537.000
>1
>
># 16 digit credit card number#
>
>2019101200
>20191019111537
>Y
>
>
>
> 
> 

It’s nice to be proven wrong on this…

For me the keys were changing the OFX Server URL in the Bank Settings tab of 
the Edit User function in the Aqbanking Setup Wizard to:
https://mobilesoa.citi.com/CitiOFXInterface 

Then using a web browser to log into Citicards and setting the 10 minute 
validation window,
and going back to the Aqbanking setup (same Bank Settings tab in Edit User) and 
clicking the [Retrieve Account List]

I have the Application Version ( in OFX-speak) set to 2700. That shows 
up as Quicken 2018. The APPVER of 2500 in the example above is close, if not 
already over, the sunset Quicken puts on downloadable transactions after 3 
years. No telling how this all will work when Quicken goes to subscription-only 
next year.

Hitting the [Retrieve Account List] button may not be necessary vs. just 
kicking off a normal data connection. But there is some chatter in the Quicken 
user community that you can’t ask for a transaction download during the 
connection request with Citi’s 10-minute validation window open. Using the 
button worked for me. I didn’t need the new account list from Citi, as my old 
account definition still worked once I got the server address fixed.

I didn’t have to mess with NEWFILEID, as aqbanking’s default works fine for me. 
(That changes with every connection, so I’m happy not to mess with it.)


--
Dave Reiser
dbrei...@icloud.com





___
gnucash-user mailing list
gnucash-user@gnucash.org
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
If you are using Nabble or Gmane, please see 
https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
-
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.


Re: [GNC] AqBanking help for Citi CC (cont'd again)

2019-10-21 Thread xngin
Greetings everyone,

I'm happy to report a working Citi CC OFX Direct Connect through AqBanking.
It took quite a bit of tinkering to figure out. For a while I was stuck on
the fact that  had to be a UUID4, which AqBanking cannot produce,
but it seems that Citi changed something and now it works as is.

It may be helpful for me to mention that I first discovered the correct OFX
request, and then got AqBanking working. A working OFX request is included
at the bottom of this message. Unfortunately, it has been a while since I
stumbled upon it and I vaguely recall that the request alone was not enough.
I am speculating now, but I think I had to enable that 10 minute window
mentioned in the thread and during it send a simple signon request (with no
transaction/statement request field). Only after it returned a success was I
able to request data.

In terms of submitting the request, I have a few working options: 
1) a POST request with the following headers 'Content-Type':
"application/x-ofx", 'User-Agent':"InetClntApp/3.0", "Accept":"*/*"
2) a call to ofxget (part of ofxtools) with the following configuration file
(~/.config/ofxtools/ofxget.cfg):

[citi]
version = 103
appver = 2500
creditcard = # 16 digit credit card number # 
org = Citigroup
fid = 24909
user = #username#
url = https://mobilesoa.citi.com/CitiOFXInterface
pretty = true
unclosedelements = true

3) AqBanking v5.7.8 with the following configuration file:
~/.aqbanking/settings/users/uid0001.conf

int  uniqueId="58"
char backendName="aqofxconnect"
char userName="username"
char userId="username "
char customerId="username "
char country="us"
char bankCode="00"
int  lastSessionId="0"

data {
  backend {
char bankName="Citi Credit Card"
char org="Citigroup"
char fid="24909"
char serverAddr="https%3A%2F%2Fmobilesoa.citi.com%2FCitiOFXInterface"
char appId="QWIN"
char appVer="2500"
char headerVer="103"
char clientUid="a fixed UUID4 string"
int  httpVMajor="0"
int  httpVMinor="0"
  } #backend
} #data



Finally, here is the working OFX request. If you find this information
useful, please consider adding it to the GnuCash wiki.

OFXHEADER:100
DATA:OFXSGML
VERSION:103
SECURITY:NONE
ENCODING:USASCII
CHARSET:1252
COMPRESSION:NONE
OLDFILEUID:NONE
NEWFILEUID:#random uuid4 or just some random large integer, like
20180912052115#




20191020111537.000
#username#
#passsword#
ENG
Citigroup24909
QWIN
2500
#uuid4, i keep it fixed between sessions, but don't
recall setting it#




20191021211537.000
1

# 16 digit credit card number#

2019101200
20191019111537
Y








--
Sent from: http://gnucash.1415818.n4.nabble.com/GnuCash-User-f1415819.html
___
gnucash-user mailing list
gnucash-user@gnucash.org
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
If you are using Nabble or Gmane, please see 
https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
-
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.


Re: [GNC] AqBanking help for Citi CC (cont'd again)

2019-10-21 Thread David Reiser via gnucash-user

> On Oct 21, 2019, at 12:13 PM, Jonathan Stickel  wrote:
> 
> On 10/20/19 22:13, John Ralls wrote:
>>> On Oct 20, 2019, at 7:46 PM, Jonathan Stickel  wrote:
>>> 
>>> As with messages in January and August, I too would like AqBanking to work 
>>> with a Citi credit card account. I've followed the recommend settings 
>>> described here:
>>> 
>>> https://lists.gnucash.org/pipermail/gnucash-user/2018-October/080548.html
>>> 
>>> but still no luck.
>>> 
>>> I did find a feature when logged in to my citi.com account to "manage 
>>> access" for third party software applications ("like Quicken® or 
>>> Quickbooks®"). This is through Profile->More Settings. Clicking on Add 
>>> Access then gives 10 minutes to make a connection. I've tried running 
>>> AqBanking during this 10 minute window, but it still does not retrieve an 
>>> account list or download transactions. So I am at a loss. If anyone is 
>>> currently being successful using a Citi cards connection, please post!
>> That 10-minute window makes it seem like it's OFX Web Connect, where you 
>> authenticate via the web and then connect with your financial software. 
>> AQBanking and therefor GnuCash doesn't support that. It supports only OFX 
>> Direct Connect where the financial software handles the authentication.
>> Regards,
>> John Ralls
> 
> Thanks for the observation. Perhaps that part is a red herring.
> 
> My main question remains:  is anyone successfully running AqBanking with Citi 
> Cards? If so, how did you make it work?
> 
> Thanks,
> Jonathan

Not anymore. I used aqbanking for many years to download Citicard transactions. 
A couple years ago the connections started failing about half the time. And a 
couple hours later, whether I got the data or not, I’d get an email from Citi 
saying they had detected suspicious activity on my account and I was required 
to change my password. Kinda weird for them to cough up all the transaction 
data, and then decide the connection was suspicious. But this is not the first 
disagreement I’ve had with Citi over weird security policies. Eventually I gave 
up on directconnect downloads. If I need Citi transactions (not often 
recently), I log in via the web interface, download the qfx file, and import 
that into Gnucash.

https://community.quicken.com/discussion/7859184/new-8-27-19-citi-cards-returning-ol-301-error#latest
 

indicates that Citi has further modified their permitted third part access, and 
even Quicken users are having problems.

I tried the old aqbanking connect attempt last night, and got no response. The 
ofx.log showed the outgoing commands, with nothing coming back. I had activated 
Citi’s 10 minute window, to no avail. I also got no notice that anyone had 
tried to break in. I’d love to see the ofx.log and conn.log from a successful 
download in Quicken of Citi transaction data. There’s a chance the old ofx 
server just drops the connection on any attempted login. 

Citi’s description of the third party authorization (once an app is authorized, 
changing your password won’t prevent access by the app…) leads me to believe 
there is some additional handshake/authentication going on during that logon in 
10 minute window that is outside the ofx spec. If so, there’s no way for 
aqbanking to handle that. I seriously doubt we’ll ever see published-standard 
ofxdirectconnect transaction downloads from Citi again. The banking regulators 
are making it hard to accomplish, Quicken would just as soon the handshake be 
totally proprietary, and the banks don’t want to bother with software 
development if they can help it.

Good luck.

--
Dave Reiser
dbrei...@icloud.com




___
gnucash-user mailing list
gnucash-user@gnucash.org
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
If you are using Nabble or Gmane, please see 
https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
-
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.


Re: [GNC] AqBanking help for Citi CC (cont'd again)

2019-10-21 Thread Jonathan Stickel

On 10/20/19 22:13, John Ralls wrote:




On Oct 20, 2019, at 7:46 PM, Jonathan Stickel  wrote:

As with messages in January and August, I too would like AqBanking to work with 
a Citi credit card account. I've followed the recommend settings described here:

https://lists.gnucash.org/pipermail/gnucash-user/2018-October/080548.html

but still no luck.

I did find a feature when logged in to my citi.com account to "manage access" for third 
party software applications ("like Quicken® or Quickbooks®"). This is through 
Profile->More Settings. Clicking on Add Access then gives 10 minutes to make a connection. I've 
tried running AqBanking during this 10 minute window, but it still does not retrieve an account list 
or download transactions. So I am at a loss. If anyone is currently being successful using a Citi 
cards connection, please post!


That 10-minute window makes it seem like it's OFX Web Connect, where you 
authenticate via the web and then connect with your financial software. 
AQBanking and therefor GnuCash doesn't support that. It supports only OFX 
Direct Connect where the financial software handles the authentication.

Regards,
John Ralls



Thanks for the observation. Perhaps that part is a red herring.

My main question remains:  is anyone successfully running AqBanking with 
Citi Cards? If so, how did you make it work?


Thanks,
Jonathan
___
gnucash-user mailing list
gnucash-user@gnucash.org
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
If you are using Nabble or Gmane, please see 
https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
-
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.


Re: [GNC] AqBanking help for Citi CC (cont'd again)

2019-10-20 Thread John Ralls


> On Oct 20, 2019, at 7:46 PM, Jonathan Stickel  wrote:
> 
> As with messages in January and August, I too would like AqBanking to work 
> with a Citi credit card account. I've followed the recommend settings 
> described here:
> 
> https://lists.gnucash.org/pipermail/gnucash-user/2018-October/080548.html
> 
> but still no luck.
> 
> I did find a feature when logged in to my citi.com account to "manage access" 
> for third party software applications ("like Quicken® or Quickbooks®"). This 
> is through Profile->More Settings. Clicking on Add Access then gives 10 
> minutes to make a connection. I've tried running AqBanking during this 10 
> minute window, but it still does not retrieve an account list or download 
> transactions. So I am at a loss. If anyone is currently being successful 
> using a Citi cards connection, please post!

That 10-minute window makes it seem like it's OFX Web Connect, where you 
authenticate via the web and then connect with your financial software. 
AQBanking and therefor GnuCash doesn't support that. It supports only OFX 
Direct Connect where the financial software handles the authentication.

Regards,
John Ralls

___
gnucash-user mailing list
gnucash-user@gnucash.org
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
If you are using Nabble or Gmane, please see 
https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
-
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.


Re: [GNC] AqBanking help for Citi CC (continued)

2019-08-19 Thread xngin
I have the same problem. When I try the settings you outlined above, with the
trailing space in the user name or without, I get the exact same log
messages (except the IP in my log is 23.205.73.7). GnuCash 3.5,  AqBanking
v5.7.8.0stable.

When I inspect the /tmp/ofx.log file, I only see the request sent, and not
received response. That's odd given that the log window inside GnuCash says
code 403 was received.

Has anyone been able to get it to work?  



--
Sent from: http://gnucash.1415818.n4.nabble.com/GnuCash-User-f1415819.html
___
gnucash-user mailing list
gnucash-user@gnucash.org
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
If you are using Nabble or Gmane, please see 
https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
-
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.


Re: [GNC] AqBanking help for Citi CC

2018-10-29 Thread Fross, Michael
Hi Jim.  I think we can end this discussion.  I decided to install v3.3 on
another windows 10 machine.  It worked. There is either something broken on
my main machine (doubtful) or some security software my employer installed
is causing the issue (more probable.)

Your "username " discovery has really been helpful and I have it working.
I may just need to move my GNC installation to my home machine instead of
my work laptop.

Your generosity in helping me troubleshoot has been amazing.  Thank you so
much.

Michael

On Mon, Oct 29, 2018 at 12:35 AM Jim Maki via gnucash-user <
gnucash-user@gnucash.org> wrote:

>
> > Accquiring lock: Started.
>
> > Accquiring lock: 2812 of 6
>
> > <..>
>
> > Accquiring lock: 59984 of 6
>
> > Accquiring lock: 5 of 6
>
> > Accquiring lock: Finished.
>
> > 3:2018/10/28
>
> >
> 11-04-37:gwen(39044):C:/gcdev64/gnucash/releases/src/gwenhywfar-4.20.0/plugins/configmgr/dir/c
>
> > fgdir.c:  469: Could not lock group [shared/certs]: 2
>
> > 3:2018/10/28
>
> >
> 11-04-37:aqbanking(39044):C:/gcdev64/gnucash/releases/src/aqbanking-5.7.8/src/libs/aqbanking/b
>
> > anking_cfg.c:  303: Could not lock shared group [certs] (-109)
>
> > 4:2018/10/28
>
> >
> 11-04-37:aqbanking(39044):C:/gcdev64/gnucash/releases/src/aqbanking-5.7.8/src/libs/aqbanking/g
>
> > ui/abgui.c:  147: Could not lock certs db, asking user (-109)
>
> This is a file locking issue and you just have to delete the ".lck" files.
> For a description of file locking see:
>
>
> https://www.gnucash.org/docs/v3/C/gnucash-guide/basics-backup1.html#basics-backuplock2
>
> For the AqBanking directory on Windows containing the lock files, see
> table 2.4 in:
>
>
> https://www.gnucash.org/docs/v3/C/gnucash-guide/basics-migrate-settings.html
>
> If you want real detail, I believe the actual locking code is fslock.c:
>
>
> https://github.com/cstim/gwenhywfar/blob/master/src/os/windows/fslock.c
>
> You'll see to lock a directory "D" they create a lock file "D/.dir.lck"
> and to lock a file "F" they lock "F.lck". These are the files you should
> delete.
>
> Those tidbits make me want to skim through the whole GnuCash Tutorial and
> Concepts Guide:
>
>  https://www.gnucash.org/docs/v3/C/gnucash-guide/
>
> > So it seems the account never gets configured into AQBanking...that's a
> hint I think. AQBanking does not record the account.
>
> Given Chase works for you but Citi only lacks the account setup, you're
> almost there. All you have to do is manually create the account part (given
> that you've created the user part).
>
> Start the AqBanking wizard: Tools ==> Online Banking Setup ... ==> Next
> ==> Start AqBanking Wizard.
>
> Edit the user you already created to verify it's correct, but don't use
> "Retrieve Account List". Once you're satisfied it's right, close the user
> and then click on Accounts ==> Create Account and fill it in (see below).
>
> Once you close the "AqBanking Setup" window just make sure it's mapped to
> the right GnuCash account and you should be good to go.
>
> For convenience, here's the configuration I posted before (updated to
> version 2900):
>
> AqBanking Setup
>
> ==>  User Settings
>
> >  User Name - "YOURUSERID"
>
> >  User Id - "YOURUSERID " (trailing space)
>
> >  Client UID - not specified
>
> ==>  Bank Settings
>
> >  Bank Name - "Citi Credit Card"
>
> >  Broker Id - "Citigroup"
>
> >  FID - "24909"
>
> >  ORG - "Citigroup"
>
> >  Server URL -
>
> "https://www.accountonline.com/cards/svc/CitiOfxManager.do;
>
> ==>  Application Settings
>
> >  Application ID - "QWIN"
>
> >  Application Version - "2900"
>
> >  Header Version - "103"
>
> >  No Special Settings
>
> ==>  Account Info
>
> >  Account Number - "YOUR CC NUMBER"
>
> >  Account Name - "Citigroup"
>
> >  IBAN - not specified
>
> >  Owner Name - not specified
>
> >  Currency - "US Dollar (USD)"
>
> >  Account Type - "Credit Card Account"
>
> ==>  Bank Info
>
> >  Country - "United States of America (US)"
>
> >  Bank Code - "www.accountonline.com"
>
> >  Bank Name - "www.accountonline.com"
>
> >  SWIFT BIC - not specified
>
> >  Selected User - the user you defined above
>
> Hope that helps.
>
>Jim
>
> ___
> gnucash-user mailing list
> gnucash-user@gnucash.org
> To update your subscription preferences or to unsubscribe:
> https://lists.gnucash.org/mailman/listinfo/gnucash-user
> If you are using Nabble or Gmane, please see
> https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
> -
> Please remember to CC this list on all your replies.
> You can do this by using Reply-To-List or Reply-All.
___
gnucash-user mailing list
gnucash-user@gnucash.org
To update your subscription preferences or to unsubscribe:

Re: [GNC] AqBanking help for Citi CC

2018-10-28 Thread Fross, Michael
Thanks a lot for the help Jim.  I'm responded to your questions inline in
RED (assuming your mail client support colors) prefaced with [FROSS].

Your information is really helpful Jim and I appreciate the time you took
to respond.  Given I can download the Chase information successfully, it
seems like AQBanking is working.but not sure why CITI works on Ubuntu
but not Windows.  I could only test v3.2 on Ubuntu, so I think I'll
downgrade my Windows version to v3.2 and see if that works.  It's a bit
more of an "apples to apples" comparison.

Michael

On Sun, Oct 28, 2018 at 2:22 AM Jim Maki via gnucash-user <
gnucash-user@gnucash.org> wrote:

>
> Three areas of comment to some potential problem areas ...
>
>
>
> ===> Windows certificate bundle is OK
>
> To verify the Windows certificate file is not an issue I copied the the
> following certificate bundle from Windows to Ubuntu:
>  C:\Program Files (x86)\gnucash\share\gwenhywfar\ca-bundle.crt
>
> On Ubuntu, Citi's cert was validated using the Windows cert bundle via
> the following command:
>  curl ... \
>  --cacert ca-bundle.crt --capath . \
>  https://www.accountonline.com/cards/svc/CitiOfxManager.do
>
> So the Windows GnuCash certificate bundle is not the issue.
>
>
> ===> Error on gnutls_bye: -24 might be some password issue
>
> Looking at:
>
>  http://mcs.une.edu.au/doc/manual/gnutls.html
>
> the theme for error code -24 (GNUTLS_E_DECRYPTION_FAILED) was about
> passwords, either no password, password not in ASCII, wrong, ... . This
> is a certificate password vs your password which is passed in the OFX
> XML and not used in the connection setup.
>
>
>
> ===> Comparing your vs my system output - where does it differ?
>
>
> Can you compare your system with the following from my Windows 10?
>
> On a powershell terminal session see what's the default text encoding
> via "[System.Text.Encoding]::Default":
>
>PS===> [System.Text.Encoding]::Default
>
>IsSingleByte  : True
>BodyName  : iso-8859-1
>EncodingName  : Western European (Windows)
>HeaderName: Windows-1252
>WebName   : Windows-1252
>WindowsCodePage   : 1252
>IsBrowserDisplay  : True
>IsBrowserSave : True
>IsMailNewsDisplay : True
>IsMailNewsSave: True
>EncoderFallback   : System.Text.InternalEncoderBestFitFallback
>DecoderFallback   : System.Text.InternalDecoderBestFitFallback
>IsReadOnly: True
>CodePage  : 1252
>
> [FROSS]  My output matches yours.

>
> On a DOS terminal session get the OS version via "ver":
>
>===> ver
>Microsoft Windows [Version 10.0.17134.376]
>

[FROSS] Mine seem seems to be a bit of an older build:  Microsoft Windows
[Version 10.0.17134.345]

>
> On the same DOS terminal see the AqBanking version:
>
>===> cd "C:\Program Files (x86)\gnucash\bin"
>===> aqbanking-cli.exe  versions
>3:2018/10/27
> 21-25-19:gwen(5224):C:/gcdev64/gnucash/releases/src/gwenhywfar-4.20.0/src/base/i18n.c:
>
> 120: No translation found for WIN32 locale [English_United States.1252]
>Versions:
> AqBanking-CLI: 5.7.8
> Gwenhywfar   : 4.20.0.0
> AqBanking: 5.7.8.0
>

[FROSS]  I have the same version as you

>
> AqBanking version 5.7.8 looks like the latest:
>https://www.aquamaniac.de/sites/download/packages.php
>
> [FROSS]  I looked earlier as well.  Looks like there is a 5.9.9 beta, but
not a stable version.
https://www.aquamaniac.de/rdm/projects/aqbanking/files


> Run aqbanking-cli to show your accounts (note the locale error message):
>
>===> REM Show the account to work with
>===> aqbanking-cli  listaccs
>3:2018/10/27
> 20-20-43:gwen(8124):C:/gcdev64/gnucash/releases/src/gwenhywfar-4.20.0/src/base/i18n.c:
>
> 120: No translation found for WIN32 locale [English_United States.1252]
>Account www.accountonline.com   YOURCCACCOUNT www.accountonline.com
> Citigroup


[FROSS] This shows a Chase credit card, but not Citibank account.  GNUCash
shows the user defined, but I don't think I ever successfully connected to
my bank.  I get the "Error on gnutls_bye: -24" error when I first attempt
to contact the bank before I ever even enter in my account password.  When
setting up a new user, but before "Retrieve Accounts" the setup tool
reaches out to the bank.  I get the following output:

TITLE: Setting Up OFX DirectConnect User
---
10:56:12 Retrieving SSL certificate
10:56:12 Connecting to server...
10:56:12 Using GnuTLS default ciphers.
10:56:12 TLS: SSL-Ciphers negotiated: TLS1.2:ECDHE-RSA-AES-256-GCM:AEAD
10:56:12 Signer not found
10:56:12 Certificate is not trusted
10:57:21 Connected.
10:57:21 Error on gnutls_bye: -24 (Decryption has failed.)
10:57:21 Disconnected.
10:57:21 Connection ok, certificate probably received
10:57:21 Operation finished, you can now close this window.

The attempt times out (I have to wait 30 seconds or so) 

Re: [GNC] AqBanking help for Citi CC

2018-10-28 Thread Jim Maki via gnucash-user


Three areas of comment to some potential problem areas ...



===> Windows certificate bundle is OK

To verify the Windows certificate file is not an issue I copied the the 
following certificate bundle from Windows to Ubuntu:

    C:\Program Files (x86)\gnucash\share\gwenhywfar\ca-bundle.crt

On Ubuntu, Citi's cert was validated using the Windows cert bundle via 
the following command:

    curl ... \
    --cacert ca-bundle.crt --capath . \
    https://www.accountonline.com/cards/svc/CitiOfxManager.do

So the Windows GnuCash certificate bundle is not the issue.


===> Error on gnutls_bye: -24 might be some password issue

Looking at:

    http://mcs.une.edu.au/doc/manual/gnutls.html

the theme for error code -24 (GNUTLS_E_DECRYPTION_FAILED) was about 
passwords, either no password, password not in ASCII, wrong, ... . This 
is a certificate password vs your password which is passed in the OFX 
XML and not used in the connection setup.




===> Comparing your vs my system output - where does it differ?


Can you compare your system with the following from my Windows 10?

On a powershell terminal session see what's the default text encoding 
via "[System.Text.Encoding]::Default":


  PS===> [System.Text.Encoding]::Default

  IsSingleByte  : True
  BodyName  : iso-8859-1
  EncodingName  : Western European (Windows)
  HeaderName    : Windows-1252
  WebName   : Windows-1252
  WindowsCodePage   : 1252
  IsBrowserDisplay  : True
  IsBrowserSave : True
  IsMailNewsDisplay : True
  IsMailNewsSave    : True
  EncoderFallback   : System.Text.InternalEncoderBestFitFallback
  DecoderFallback   : System.Text.InternalDecoderBestFitFallback
  IsReadOnly    : True
  CodePage  : 1252


On a DOS terminal session get the OS version via "ver":

  ===> ver
  Microsoft Windows [Version 10.0.17134.376]


On the same DOS terminal see the AqBanking version:

  ===> cd "C:\Program Files (x86)\gnucash\bin"
  ===> aqbanking-cli.exe  versions
  3:2018/10/27 
21-25-19:gwen(5224):C:/gcdev64/gnucash/releases/src/gwenhywfar-4.20.0/src/base/i18n.c: 
120: No translation found for WIN32 locale [English_United States.1252]

  Versions:
   AqBanking-CLI: 5.7.8
   Gwenhywfar   : 4.20.0.0
   AqBanking    : 5.7.8.0


AqBanking version 5.7.8 looks like the latest:
  https://www.aquamaniac.de/sites/download/packages.php


Run aqbanking-cli to show your accounts (note the locale error message):

  ===> REM Show the account to work with
  ===> aqbanking-cli  listaccs
  3:2018/10/27 
20-20-43:gwen(8124):C:/gcdev64/gnucash/releases/src/gwenhywfar-4.20.0/src/base/i18n.c: 
120: No translation found for WIN32 locale [English_United States.1252]
  Account www.accountonline.com   YOURCCACCOUNT www.accountonline.com   
Citigroup



Make a request that will show the details of the cert request (password 
required).

I'd be curious as to how your output differs:

  ===> aqbanking-cli  request --balance
  3:2018/10/27 
20-14-37:gwen(10536):C:/gcdev64/gnucash/releases/src/gwenhywfar-4.20.0/src/base/i18n.c: 
120: No translation found for WIN32 locale [English_United States.1252]

  = Executing Jobs =
  AqBanking v5.7.8.0stable
  Sending jobs to the bank(s)
  Locking user YOURUSERID
  = Enter Password =
  Please enter the password for user YOURUSERID
  Input: YOURPASSWORD
  3:2018/10/27 
20-14-44:(null)(10536):C:/gcdev64/gnucash/releases/src/aqbanking-5.7.8/src/plugins/backends/aqofxconnect/plugin/network.c: 
82: Saving response in "/tmp/ofx.log" ...

  Saving communication log to /tmp/ofx.log
  Sending request...
  Connecting to server...
  Resolving hostname "www.accountonline.com" ...
  IP address is "104.65.4.169"
  Connecting to "www.accountonline.com"
  Connected to "www.accountonline.com"
  Using GnuTLS default ciphers.
  TLS: SSL-Ciphers negotiated: TLS1.2:ECDHE-RSA-AES-256-GCM:AEAD
  Signer not found
  Certificate is not trusted
  5:2018/10/27 
20-14-44:aqbanking(10536):C:/gcdev64/gnucash/releases/src/aqbanking-5.7.8/src/libs/aqbanking/gui/abgui.c: 
165: Automatically accepting certificate 
[D0:7D:90:E7:63:F0:59:E0:CE:D2:62:82:61:4A:68:68]

  Connected.
  Sending message...
  Message sent.
  Waiting for response...
  Receiving response...
  HTTP-Status: 200 (OK)
  Response received.
  Disconnecting from server...
  Disconnected.
  Parsing response...
  3:2018/10/27 
20-14-45:(null)(10536):C:/gcdev64/gnucash/releases/src/aqbanking-5.7.8/src/plugins/backends/aqofxconnect/plugin/network.c: 
171: Saving response in "/tmp/ofx.log" ...

  Parsing response
  Status for signon request: Success (Code 0, severity "INFO")
  The server successfully processed the request.
  Status for transaction statement request: Success (Code 0, severity 
"INFO")

  The server successfully processed the request.
  Unlocking user YOURUSERID
  Executing Jobs: 1 of 1
  Postprocessing jobs
  Job Get Balance: finished
  Resetting provider queues
  Executing Jobs: Finished.
  ...

At some point 

Re: [GNC] AqBanking help for Citi CC

2018-10-27 Thread Fross, Michael
Hello everyone,

I was able to get the download to work without issue using Jim's "space"
modification on Ubuntu with Gnucash v2.6.19 and on v3.2.   I have been
unable to get v3.3 to download on Windows.

It seems to just be an issue with windows.  I don't get the

*Error on gnutls_bye: -24 (Decryption has failed.)*

in Ubuntu with either 2.6.19 or 3.2.

Michael

On Thu, Oct 25, 2018 at 9:15 AM Fross, Michael  wrote:

> Interesting!
>
> I installed the GNUCash v2.6.19 on Ubuntu (the one in the repo) and it
> worked fine!  I'm going to try v3.3 on Ubuntu and see if I can narrow this
> down to a windows problem (which is my assumption) or a 3.3 issue for me.
>
> Thanks.  I'll report back when I have additional information.
>
> Michael
>
> On Wed, Oct 24, 2018 at 9:17 AM Fross, Michael  wrote:
>
>> Hello Jim,
>>
>> This is great news.  I had the Citibank Credit Card download working for
>> years, but it broke early this year.  I've attempted to setup GNUCash based
>> on the above, but continue to struggle.  I receive the following error
>> during the initial bank connection:
>>
>> *Error on gnutls_bye: -24 (Decryption has failed.)*
>>
>> After looking at your OFX settings above, I used the following during the
>> GNUCash setup:
>>
>>- Create User - Select OFX
>>- Bank Name:  Citi Credit Card
>>- Broker Id:
>>- FID: 24909
>>- ORG: Citigroup
>>- Server URL:
>>https://www.accountonline.com/cards/svc/CitiOfxManager.do
>>- User Name: myusername
>>- User Id: myusername<--- I added a space per your comments
>>- Client UID:
>>- Emulated App: Quicken 2013
>>- Application ID: QWIN
>>- Application Version: 2400
>>- Header Version: 103
>>
>> After accepting the certificate , the log window has that error.  If I
>> retrieve accounts after this, I get the following:
>>
>> 09:12:27 Sending request...
>> 09:12:27 Using GnuTLS default ciphers.
>> 09:12:28 TLS: SSL-Ciphers negotiated: TLS1.2:ECDHE-RSA-AES-256-GCM:AEAD
>> 09:12:28 Signer not found
>> 09:12:28 Certificate is not trusted
>> 09:13:31 Waiting for response...
>> 09:13:31 No message received
>> 09:13:31 Network error while waiting for response
>> 09:13:31 Operation finished, you can now close this window.
>>
>> I have a long password, but no special characters in it.  I'm on windows
>> and need to read up a bit more on how to get the OFX.log.  Setting the ENV
>> variable and starting GNUCash from the command session didn't seem to
>> produce one.
>>
>> I appreciate the guidance and the time.  I'm sure a lot of people use
>> Citi Cards and your debugging can benefit a lot of people.  Can you provide
>> any differences in your GNUCash config settings that what I have above?
>> I've tried a few variations but to no avail.
>>
>> Thank you!
>>
>> Michael
>>
>>
>> On Tue, Oct 23, 2018 at 11:12 PM Jim Maki via gnucash-user <
>> gnucash-user@gnucash.org> wrote:
>>
>>> I just successfully set up GnuCash to download Citi credit card data
>>> using AqBanking - for now all you have to do is add a space to the end
>>> of your userid (assuming everything else is correct).The issue seems to
>>> be with Citi ...
>>>
>>> When it consistently failed with code 403, I turned on OFX logging
>>> (export AQOFX_LOG_COMM=1), snagged the OFX request (from /tmp/ofx.log),
>>> formatted it to make it more readable, and created a bash script using
>>> curl to make the OFX request. Paradoxically it worked while the
>>> equivalent un-beautified GnuCash request failed.
>>>
>>> After little debugging, the key lines in the GnuCash ofx.log were:
>>>
>>> == OFX ==
>>> ...
>>> ... myuserid
>>> mypassword
>>> ...
>>> == OFX ==
>>>
>>> The above will work if you add a space either at the end of the
>>> "...myuserid" line, or before "" in the next line. At
>>> the GnuCash user interface level that involves adding a trailing space
>>> to the AqBanking userid for Citi.
>>>
>>> For reference, below is the OFX template file I use to feed my
>>> curl-based script. Eventually GnuCash makes an equivalent request.
>>> (Again, eliminate the leading spaces before "" and it, too
>>> fails.)
>>>
>>> == OFX ==
>>> OFXHEADER:100
>>> DATA:OFXSGML
>>> VERSION:103
>>> SECURITY:NONE
>>> ENCODING:USASCII
>>> CHARSET:1252
>>> COMPRESSION:NONE
>>> OLDFILEUID:NONE
>>> NEWFILEUID:$OFX_DATETIME
>>>
>>> 
>>> 
>>> 
>>> $OFX_DATETIME
>>> $OFX_USER
>>> $OFX_PW
>>> ENG
>>> 
>>> $OFX_ORG
>>> $OFX_FID
>>> 
>>> QWIN
>>> 2400
>>> 
>>> 
>>> 
>>> 
>>> $OFX_DATETIME
>>> 1
>>> 
>>> 
>>> $OFX_ACCOUNT
>>> 
>>> 
>>> $OFX_STARTDATE
>>> $OFX_ENDDATE
>>> Y
>>> 
>>> 
>>> 
>>> 
>>> 
>>> == OFX ==
>>>
>>> If GnuCash did prettified SGML it would avoid this problem with Citi's
>>> parsing.
>>>
>>>Jim
>>>
>>> ___
>>> gnucash-user mailing list
>>> gnucash-user@gnucash.org
>>> To update your subscription preferences or to 

Re: [GNC] AqBanking help for Citi CC

2018-10-25 Thread Jim Maki via gnucash-user


> I installed the GNUCash v2.6.19 on Ubuntu (the one in the repo) and 
it worked fine!  I'm going to try v3.3 on Ubuntu and see if I can narrow 
this down to a windows problem (which is my assumption) or a 3.3 issue 
for me.


Here's a summary of what I've found so far:

1. On Ubuntu 18.04, GnuCash 2.6.19 with a blank appended to the Citi 
userid works. I could not automatically generate Citi accounts and had 
to manually enter them.


2. I upgraded to Ubuntu 18.10 giving GnuCash 3.3 which worked 
identically to 18.04/2.6.19.


3. On Windows 10 I installed GnuCash 3.3 with almost identical results 
except for the already-mentioned "Signer not found" and "Certificate is 
not trusted" messages (which did not affect functionality):


    That cert-related problem was already discussed (without 
resolution) in the post "Online Transactions - Sender Not Found" found 
at 
https://lists.gnucash.org/pipermail/gnucash-user/2018-March/075406.html 
( ironically started by the same author as started this thread at 
https://lists.gnucash.org/pipermail/gnucash-user/2018-June/077627.html ).


    I'm going to assume the "Signer not found" problem is a bug report 
as opposed to something users are going to resolve. As far as I can tell 
it's a Windows-only problem that doesn't affect functionality.


4. To setup/tear-down the capture of the OFX log on Windows, at the 
command line:


REM Setup OFX capture.
mkdir C:\tmp
setx AQOFX_LOG_COMM "1"
REM check AQOFX_LOG_COMM value
reg query HKCU\Environment
...
REM Start GnuCash and look at C:\tmp\ofx.log contents.
...
REM Tear down OFX capture.
reg delete HKCU\Environment /v AQOFX_LOG_COMM /f
reg query HKCU\Environment
rmdir /s /q C:\tmp

The only strange part of the Windows OFX capture was that the lines 
ended with CR-CR-LF. I copied the OFX log file to my Ubuntu system, 
edited it down to only the request lines, removed the trailing userid 
blank, and used it in a curl request to Citi that worked! So a trailing 
blank or CR works :)


5. The last puzzle to me is trying to decipher why it works for David 
Reiser:


    "I had been running with AppVer=2500. I changed that to 2700 last 
night and both Chase and Citicards resumed working from within gnucash." 
(See 
https://lists.gnucash.org/pipermail/gnucash-user/2018-October/080467.html )


    On a side note, his post last December had some good information 
about application version and introduced me to the aqbanking-cli 
software (see 
https://lists.gnucash.org/pipermail/gnucash-user/2017-December/073781.html 
). I'm going to play a bit with "aqbanking-cli ...".


  Jim


___
gnucash-user mailing list
gnucash-user@gnucash.org
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
If you are using Nabble or Gmane, please see 
https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
-
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.

Re: [GNC] AqBanking help for Citi CC

2018-10-25 Thread Fross, Michael
Interesting!

I installed the GNUCash v2.6.19 on Ubuntu (the one in the repo) and it
worked fine!  I'm going to try v3.3 on Ubuntu and see if I can narrow this
down to a windows problem (which is my assumption) or a 3.3 issue for me.

Thanks.  I'll report back when I have additional information.

Michael

On Wed, Oct 24, 2018 at 9:17 AM Fross, Michael  wrote:

> Hello Jim,
>
> This is great news.  I had the Citibank Credit Card download working for
> years, but it broke early this year.  I've attempted to setup GNUCash based
> on the above, but continue to struggle.  I receive the following error
> during the initial bank connection:
>
> *Error on gnutls_bye: -24 (Decryption has failed.)*
>
> After looking at your OFX settings above, I used the following during the
> GNUCash setup:
>
>- Create User - Select OFX
>- Bank Name:  Citi Credit Card
>- Broker Id:
>- FID: 24909
>- ORG: Citigroup
>- Server URL: https://www.accountonline.com/cards/svc/CitiOfxManager.do
>- User Name: myusername
>- User Id: myusername<--- I added a space per your comments
>- Client UID:
>- Emulated App: Quicken 2013
>- Application ID: QWIN
>- Application Version: 2400
>- Header Version: 103
>
> After accepting the certificate , the log window has that error.  If I
> retrieve accounts after this, I get the following:
>
> 09:12:27 Sending request...
> 09:12:27 Using GnuTLS default ciphers.
> 09:12:28 TLS: SSL-Ciphers negotiated: TLS1.2:ECDHE-RSA-AES-256-GCM:AEAD
> 09:12:28 Signer not found
> 09:12:28 Certificate is not trusted
> 09:13:31 Waiting for response...
> 09:13:31 No message received
> 09:13:31 Network error while waiting for response
> 09:13:31 Operation finished, you can now close this window.
>
> I have a long password, but no special characters in it.  I'm on windows
> and need to read up a bit more on how to get the OFX.log.  Setting the ENV
> variable and starting GNUCash from the command session didn't seem to
> produce one.
>
> I appreciate the guidance and the time.  I'm sure a lot of people use Citi
> Cards and your debugging can benefit a lot of people.  Can you provide any
> differences in your GNUCash config settings that what I have above?  I've
> tried a few variations but to no avail.
>
> Thank you!
>
> Michael
>
>
> On Tue, Oct 23, 2018 at 11:12 PM Jim Maki via gnucash-user <
> gnucash-user@gnucash.org> wrote:
>
>> I just successfully set up GnuCash to download Citi credit card data
>> using AqBanking - for now all you have to do is add a space to the end
>> of your userid (assuming everything else is correct).The issue seems to
>> be with Citi ...
>>
>> When it consistently failed with code 403, I turned on OFX logging
>> (export AQOFX_LOG_COMM=1), snagged the OFX request (from /tmp/ofx.log),
>> formatted it to make it more readable, and created a bash script using
>> curl to make the OFX request. Paradoxically it worked while the
>> equivalent un-beautified GnuCash request failed.
>>
>> After little debugging, the key lines in the GnuCash ofx.log were:
>>
>> == OFX ==
>> ...
>> ... myuserid
>> mypassword
>> ...
>> == OFX ==
>>
>> The above will work if you add a space either at the end of the
>> "...myuserid" line, or before "" in the next line. At
>> the GnuCash user interface level that involves adding a trailing space
>> to the AqBanking userid for Citi.
>>
>> For reference, below is the OFX template file I use to feed my
>> curl-based script. Eventually GnuCash makes an equivalent request.
>> (Again, eliminate the leading spaces before "" and it, too
>> fails.)
>>
>> == OFX ==
>> OFXHEADER:100
>> DATA:OFXSGML
>> VERSION:103
>> SECURITY:NONE
>> ENCODING:USASCII
>> CHARSET:1252
>> COMPRESSION:NONE
>> OLDFILEUID:NONE
>> NEWFILEUID:$OFX_DATETIME
>>
>> 
>> 
>> 
>> $OFX_DATETIME
>> $OFX_USER
>> $OFX_PW
>> ENG
>> 
>> $OFX_ORG
>> $OFX_FID
>> 
>> QWIN
>> 2400
>> 
>> 
>> 
>> 
>> $OFX_DATETIME
>> 1
>> 
>> 
>> $OFX_ACCOUNT
>> 
>> 
>> $OFX_STARTDATE
>> $OFX_ENDDATE
>> Y
>> 
>> 
>> 
>> 
>> 
>> == OFX ==
>>
>> If GnuCash did prettified SGML it would avoid this problem with Citi's
>> parsing.
>>
>>Jim
>>
>> ___
>> gnucash-user mailing list
>> gnucash-user@gnucash.org
>> To update your subscription preferences or to unsubscribe:
>> https://lists.gnucash.org/mailman/listinfo/gnucash-user
>> If you are using Nabble or Gmane, please see
>> https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
>> -
>> Please remember to CC this list on all your replies.
>> You can do this by using Reply-To-List or Reply-All.
>
>
___
gnucash-user mailing list
gnucash-user@gnucash.org
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
If you are using Nabble or Gmane, please see 

Re: [GNC] AqBanking help for Citi CC

2018-10-25 Thread Fross, Michael
Thanks Jim.  I can't seem to get AQBanking to log correctly in Windows 10.
I'll compile it on Ubuntu and try it there.  Be back shortly :)

Michael

On Thu, Oct 25, 2018 at 12:50 AM Jim Maki via gnucash-user <
gnucash-user@gnucash.org> wrote:

>
>  > I changed that to 2700 last night and both Chase and Citicards
> resumed working from within gnucash. I believe Quicken 2019 is
> AppVer=2800, but I’m not sure.
>
>
> Can you list your sanitized configuration parameters as I have? I'd like
> to compare them.
>
> And can you get your working (sanitized) ofx.log file? Does it differ
> from mine which has  followed by  on the first byte of
> the next line:
>
> >/== OFX == />/... />/... myuserid
> />/mypassword />/... />/== OFX ==
> /
>
> Here's why I'm so curious.
>
> My first test was to try Application Version 2700 and 2900: both worked
> with my blank-padded userid and both failed with my non-blank-padded
> userid. I suspect Liang's would also. But your's clearly wouldn't.
>
> So how could yours possibly work? One way is that somehow your OFXSGML
> interjects a tag between  and . So I fired up my
> trusty curl-based script doing just that by sticking the ""
> tag between:
>
>  ...
>
> 20181024221016.000MYUSERIDWITHOUTBLANK
>  ENG
>  MYPASSWORD
>  ...
>
>   And it worked without blank padding the userid (the results you
> found). So if your version of GnuCash based on your exact configuration
> inputs creates an OFXSGML file (ofx.log) different from mine (and
> Liang's) in just the right way, yours could work.
>
> Feedback would be appreciated. I'd like to see the magic that makes
> yours work. I was running 2.6.19 at first but am running 3.3 now.
>
>Jim
>
>
>
> ___
> gnucash-user mailing list
> gnucash-user@gnucash.org
> To update your subscription preferences or to unsubscribe:
> https://lists.gnucash.org/mailman/listinfo/gnucash-user
> If you are using Nabble or Gmane, please see
> https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
> -
> Please remember to CC this list on all your replies.
> You can do this by using Reply-To-List or Reply-All.
___
gnucash-user mailing list
gnucash-user@gnucash.org
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
If you are using Nabble or Gmane, please see 
https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
-
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.

Re: [GNC] AqBanking help for Citi CC

2018-10-24 Thread Jim Maki via gnucash-user


> I changed that to 2700 last night and both Chase and Citicards 
resumed working from within gnucash. I believe Quicken 2019 is 
AppVer=2800, but I’m not sure.



Can you list your sanitized configuration parameters as I have? I'd like 
to compare them.


And can you get your working (sanitized) ofx.log file? Does it differ 
from mine which has  followed by  on the first byte of 
the next line:



/== OFX == />/... />/... myuserid 
/>/mypassword />/... />/== OFX == /


Here's why I'm so curious.

My first test was to try Application Version 2700 and 2900: both worked 
with my blank-padded userid and both failed with my non-blank-padded 
userid. I suspect Liang's would also. But your's clearly wouldn't.


So how could yours possibly work? One way is that somehow your OFXSGML 
interjects a tag between  and . So I fired up my 
trusty curl-based script doing just that by sticking the "" 
tag between:


    ...
20181024221016.000MYUSERIDWITHOUTBLANK
    ENG
    MYPASSWORD
    ...

 And it worked without blank padding the userid (the results you 
found). So if your version of GnuCash based on your exact configuration 
inputs creates an OFXSGML file (ofx.log) different from mine (and 
Liang's) in just the right way, yours could work.


Feedback would be appreciated. I'd like to see the magic that makes 
yours work. I was running 2.6.19 at first but am running 3.3 now.


  Jim



___
gnucash-user mailing list
gnucash-user@gnucash.org
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
If you are using Nabble or Gmane, please see 
https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
-
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.

Re: [GNC] AqBanking help for Citi CC

2018-10-24 Thread Jim Maki via gnucash-user


< Can you provide any differences in your GnuCash config settings that 
what I have above?



Here goes my settings:

  AqBanking Setup

  ==>  User Settings
  >  User Name - "YOURUSERID"
  >  User Id - "YOURUSERID " (trailing space)
  >  Client UID - not specified
  ==>  Bank Settings
  >  Bank Name - "Citi Credit Card"
  >  Broker Id - "Citigroup"
  >  FID - "24909"
  >  ORG - "Citigroup"
  >  Server URL - 
"https://www.accountonline.com/cards/svc/CitiOfxManager.do;

  ==>  Application Settings
  >  Application ID - "QWIN"
  >  Application Version - "2400"
  >  Header Version - "103"
  >  No Special Settings

  ==>  Account Info
  >  Account Number - "YOUR CC NUMBER"
  >  Account Name - "Citigroup"
  >  IBAN - not specified
  >  Owner Name - not specified
  >  Currency - "US Dollar (USD)"
  >  Account Type - "Credit Card Account"
  ==>  Bank Info
  >  Country - "United States of America (US)"
  >  Bank Code - "www.accountonline.com"
  >  Bank Name - "www.accountonline.com"
  >  SWIFT BIC - not specified
  >  Selected User - the user you defined above



> After accepting the certificate , the log window has that error. If I 
retrieve accounts after this, I get the following:

> 09:12:27 Sending request...
> 09:12:27 Using GnuTLS default ciphers.
> 09:12:28 TLS: SSL-Ciphers negotiated: TLS1.2:ECDHE-RSA-AES-256-GCM:AEAD
> 09:12:28 Signer not found
> 09:12:28 Certificate is not trusted
> 09:13:31 Waiting for response...
> 09:13:31 No message received
> 09:13:31 Network error while waiting for response
> 09:13:31 Operation finished, you can now close this window.


Little help, but you'll find the "Signer not found" and "Certificate is 
not trusted" in:

https://github.com/cstim/gwenhywfar/blob/master/src/sio/syncio_tls.c

So those errors relate to the certificate presented by the site you 
used. First make sure you're running a current version of 
GnuCash/AqBanking and update your settings (especially check the URL). 
The certificate I get validates OK:


* Server certificate:
*  subject: businessCategory=Private Organization; jurisdictionC=US; 
jurisdictionST=Delaware; serialNumber=2154254; C=US; ST=New York; L=New 
York; O=Citigroup Inc.; OU=Web Hosting Group; CN=www.accountonline.com

*  start date: Aug 15 00:00:00 2018 GMT
*  expire date: Jan  2 12:00:00 2020 GMT
*  subjectAltName: host "www.accountonline.com" matched cert's 
"www.accountonline.com"
*  issuer: C=US; O=DigiCert Inc; OU=www.digicert.com; CN=DigiCert SHA2 
Extended Validation Server CA

*  SSL certificate verify ok.


  Jim


___
gnucash-user mailing list
gnucash-user@gnucash.org
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
If you are using Nabble or Gmane, please see 
https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
-
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.

Re: [GNC] AqBanking help for Citi CC

2018-10-24 Thread David Reiser via gnucash-user
My experience this week suggests that your Application Version setting is at 
least sufficient to cause your problem. Direct connection from gnucash to 
citicards stopped working for me earlier this year, and any time I attempted to 
make the connection, Citi decided someone was trying break into my account and 
a couple hours later would require me to reset my password (providing erroneous 
information about what constituted a valid password, argh). Since Citi would 
never tell me why they thought someone was trying to break into my account, I 
gave up on them after a while.

But when Chase stopped responding to requests for transaction data from gnucash 
this week, I figured out that something else was amiss. Quicken has always 
disabled data connections after 3-3.5 years from any version release. They’ll 
give you an informative message if you’re using Quicken, but either aqbanking 
or gnucash  haven’t handled such messages. I had been running with AppVer=2500. 
I changed that to 2700 last night and both Chase and Citicards resumed working 
from within gnucash. I believe Quicken 2019 is AppVer=2800, but I’m not sure.
--
Dave Reiser
dbrei...@icloud.com





> On Oct 24, 2018, at 10:17 AM, Fross, Michael  wrote:
> 
> Hello Jim,
> 
> This is great news.  I had the Citibank Credit Card download working for
> years, but it broke early this year.  I've attempted to setup GNUCash based
> on the above, but continue to struggle.  I receive the following error
> during the initial bank connection:
> 
> *Error on gnutls_bye: -24 (Decryption has failed.)*
> 
> After looking at your OFX settings above, I used the following during the
> GNUCash setup:
> 
>   - Create User - Select OFX
>   - Bank Name:  Citi Credit Card
>   - Broker Id:
>   - FID: 24909
>   - ORG: Citigroup
>   - Server URL: https://www.accountonline.com/cards/svc/CitiOfxManager.do
>   - User Name: myusername
>   - User Id: myusername<--- I added a space per your comments
>   - Client UID:
>   - Emulated App: Quicken 2013
>   - Application ID: QWIN
>   - Application Version: 2400
>   - Header Version: 103
> 
> After accepting the certificate , the log window has that error.  If I
> retrieve accounts after this, I get the following:
> 
> 09:12:27 Sending request...
> 09:12:27 Using GnuTLS default ciphers.
> 09:12:28 TLS: SSL-Ciphers negotiated: TLS1.2:ECDHE-RSA-AES-256-GCM:AEAD
> 09:12:28 Signer not found
> 09:12:28 Certificate is not trusted
> 09:13:31 Waiting for response...
> 09:13:31 No message received
> 09:13:31 Network error while waiting for response
> 09:13:31 Operation finished, you can now close this window.
> 
> I have a long password, but no special characters in it.  I'm on windows
> and need to read up a bit more on how to get the OFX.log.  Setting the ENV
> variable and starting GNUCash from the command session didn't seem to
> produce one.
> 
> I appreciate the guidance and the time.  I'm sure a lot of people use Citi
> Cards and your debugging can benefit a lot of people.  Can you provide any
> differences in your GNUCash config settings that what I have above?  I've
> tried a few variations but to no avail.
> 
> Thank you!
> 
> Michael
> 
> 
> On Tue, Oct 23, 2018 at 11:12 PM Jim Maki via gnucash-user <
> gnucash-user@gnucash.org> wrote:
> 
>> I just successfully set up GnuCash to download Citi credit card data
>> using AqBanking - for now all you have to do is add a space to the end
>> of your userid (assuming everything else is correct).The issue seems to
>> be with Citi ...
>> 
>> When it consistently failed with code 403, I turned on OFX logging
>> (export AQOFX_LOG_COMM=1), snagged the OFX request (from /tmp/ofx.log),
>> formatted it to make it more readable, and created a bash script using
>> curl to make the OFX request. Paradoxically it worked while the
>> equivalent un-beautified GnuCash request failed.
>> 
>> After little debugging, the key lines in the GnuCash ofx.log were:
>> 
>> == OFX ==
>> ...
>> ... myuserid
>> mypassword
>> ...
>> == OFX ==
>> 
>> The above will work if you add a space either at the end of the
>> "...myuserid" line, or before "" in the next line. At
>> the GnuCash user interface level that involves adding a trailing space
>> to the AqBanking userid for Citi.
>> 
>> For reference, below is the OFX template file I use to feed my
>> curl-based script. Eventually GnuCash makes an equivalent request.
>> (Again, eliminate the leading spaces before "" and it, too
>> fails.)
>> 
>> == OFX ==
>> OFXHEADER:100
>> DATA:OFXSGML
>> VERSION:103
>> SECURITY:NONE
>> ENCODING:USASCII
>> CHARSET:1252
>> COMPRESSION:NONE
>> OLDFILEUID:NONE
>> NEWFILEUID:$OFX_DATETIME
>> 
>> 
>> 
>> 
>> $OFX_DATETIME
>> $OFX_USER
>> $OFX_PW
>> ENG
>> 
>> $OFX_ORG
>> $OFX_FID
>> 
>> QWIN
>> 2400
>> 
>> 
>> 
>> 
>> $OFX_DATETIME
>> 1
>> 
>> 
>> $OFX_ACCOUNT
>> 
>> 
>> $OFX_STARTDATE
>> $OFX_ENDDATE
>> Y
>> 
>> 
>> 
>> 
>> 
>> 

Re: [GNC] AqBanking help for Citi CC

2018-10-24 Thread Fross, Michael
Hello Jim,

This is great news.  I had the Citibank Credit Card download working for
years, but it broke early this year.  I've attempted to setup GNUCash based
on the above, but continue to struggle.  I receive the following error
during the initial bank connection:

*Error on gnutls_bye: -24 (Decryption has failed.)*

After looking at your OFX settings above, I used the following during the
GNUCash setup:

   - Create User - Select OFX
   - Bank Name:  Citi Credit Card
   - Broker Id:
   - FID: 24909
   - ORG: Citigroup
   - Server URL: https://www.accountonline.com/cards/svc/CitiOfxManager.do
   - User Name: myusername
   - User Id: myusername<--- I added a space per your comments
   - Client UID:
   - Emulated App: Quicken 2013
   - Application ID: QWIN
   - Application Version: 2400
   - Header Version: 103

After accepting the certificate , the log window has that error.  If I
retrieve accounts after this, I get the following:

09:12:27 Sending request...
09:12:27 Using GnuTLS default ciphers.
09:12:28 TLS: SSL-Ciphers negotiated: TLS1.2:ECDHE-RSA-AES-256-GCM:AEAD
09:12:28 Signer not found
09:12:28 Certificate is not trusted
09:13:31 Waiting for response...
09:13:31 No message received
09:13:31 Network error while waiting for response
09:13:31 Operation finished, you can now close this window.

I have a long password, but no special characters in it.  I'm on windows
and need to read up a bit more on how to get the OFX.log.  Setting the ENV
variable and starting GNUCash from the command session didn't seem to
produce one.

I appreciate the guidance and the time.  I'm sure a lot of people use Citi
Cards and your debugging can benefit a lot of people.  Can you provide any
differences in your GNUCash config settings that what I have above?  I've
tried a few variations but to no avail.

Thank you!

Michael


On Tue, Oct 23, 2018 at 11:12 PM Jim Maki via gnucash-user <
gnucash-user@gnucash.org> wrote:

> I just successfully set up GnuCash to download Citi credit card data
> using AqBanking - for now all you have to do is add a space to the end
> of your userid (assuming everything else is correct).The issue seems to
> be with Citi ...
>
> When it consistently failed with code 403, I turned on OFX logging
> (export AQOFX_LOG_COMM=1), snagged the OFX request (from /tmp/ofx.log),
> formatted it to make it more readable, and created a bash script using
> curl to make the OFX request. Paradoxically it worked while the
> equivalent un-beautified GnuCash request failed.
>
> After little debugging, the key lines in the GnuCash ofx.log were:
>
> == OFX ==
> ...
> ... myuserid
> mypassword
> ...
> == OFX ==
>
> The above will work if you add a space either at the end of the
> "...myuserid" line, or before "" in the next line. At
> the GnuCash user interface level that involves adding a trailing space
> to the AqBanking userid for Citi.
>
> For reference, below is the OFX template file I use to feed my
> curl-based script. Eventually GnuCash makes an equivalent request.
> (Again, eliminate the leading spaces before "" and it, too
> fails.)
>
> == OFX ==
> OFXHEADER:100
> DATA:OFXSGML
> VERSION:103
> SECURITY:NONE
> ENCODING:USASCII
> CHARSET:1252
> COMPRESSION:NONE
> OLDFILEUID:NONE
> NEWFILEUID:$OFX_DATETIME
>
> 
> 
> 
> $OFX_DATETIME
> $OFX_USER
> $OFX_PW
> ENG
> 
> $OFX_ORG
> $OFX_FID
> 
> QWIN
> 2400
> 
> 
> 
> 
> $OFX_DATETIME
> 1
> 
> 
> $OFX_ACCOUNT
> 
> 
> $OFX_STARTDATE
> $OFX_ENDDATE
> Y
> 
> 
> 
> 
> 
> == OFX ==
>
> If GnuCash did prettified SGML it would avoid this problem with Citi's
> parsing.
>
>Jim
>
> ___
> gnucash-user mailing list
> gnucash-user@gnucash.org
> To update your subscription preferences or to unsubscribe:
> https://lists.gnucash.org/mailman/listinfo/gnucash-user
> If you are using Nabble or Gmane, please see
> https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
> -
> Please remember to CC this list on all your replies.
> You can do this by using Reply-To-List or Reply-All.
___
gnucash-user mailing list
gnucash-user@gnucash.org
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
If you are using Nabble or Gmane, please see 
https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
-
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.


Re: [GNC] AqBanking help for Citi CC

2018-10-23 Thread Liang Wang
Thanks! It works for my Citi Costco card.
On Tue, Oct 23, 2018 at 9:12 PM Jim Maki via gnucash-user
 wrote:
>
> I just successfully set up GnuCash to download Citi credit card data
> using AqBanking - for now all you have to do is add a space to the end
> of your userid (assuming everything else is correct).The issue seems to
> be with Citi ...
>
> When it consistently failed with code 403, I turned on OFX logging
> (export AQOFX_LOG_COMM=1), snagged the OFX request (from /tmp/ofx.log),
> formatted it to make it more readable, and created a bash script using
> curl to make the OFX request. Paradoxically it worked while the
> equivalent un-beautified GnuCash request failed.
>
> After little debugging, the key lines in the GnuCash ofx.log were:
>
> == OFX ==
> ...
> ... myuserid
> mypassword
> ...
> == OFX ==
>
> The above will work if you add a space either at the end of the
> "...myuserid" line, or before "" in the next line. At
> the GnuCash user interface level that involves adding a trailing space
> to the AqBanking userid for Citi.
>
> For reference, below is the OFX template file I use to feed my
> curl-based script. Eventually GnuCash makes an equivalent request.
> (Again, eliminate the leading spaces before "" and it, too fails.)
>
> == OFX ==
> OFXHEADER:100
> DATA:OFXSGML
> VERSION:103
> SECURITY:NONE
> ENCODING:USASCII
> CHARSET:1252
> COMPRESSION:NONE
> OLDFILEUID:NONE
> NEWFILEUID:$OFX_DATETIME
>
> 
> 
> 
> $OFX_DATETIME
> $OFX_USER
> $OFX_PW
> ENG
> 
> $OFX_ORG
> $OFX_FID
> 
> QWIN
> 2400
> 
> 
> 
> 
> $OFX_DATETIME
> 1
> 
> 
> $OFX_ACCOUNT
> 
> 
> $OFX_STARTDATE
> $OFX_ENDDATE
> Y
> 
> 
> 
> 
> 
> == OFX ==
>
> If GnuCash did prettified SGML it would avoid this problem with Citi's
> parsing.
>
>Jim
>
> ___
> gnucash-user mailing list
> gnucash-user@gnucash.org
> To update your subscription preferences or to unsubscribe:
> https://lists.gnucash.org/mailman/listinfo/gnucash-user
> If you are using Nabble or Gmane, please see 
> https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
> -
> Please remember to CC this list on all your replies.
> You can do this by using Reply-To-List or Reply-All.
___
gnucash-user mailing list
gnucash-user@gnucash.org
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
If you are using Nabble or Gmane, please see 
https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
-
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.


Re: [GNC] AqBanking help for Citi CC

2018-10-23 Thread Jim Maki via gnucash-user
I just successfully set up GnuCash to download Citi credit card data 
using AqBanking - for now all you have to do is add a space to the end 
of your userid (assuming everything else is correct).The issue seems to 
be with Citi ...


When it consistently failed with code 403, I turned on OFX logging 
(export AQOFX_LOG_COMM=1), snagged the OFX request (from /tmp/ofx.log), 
formatted it to make it more readable, and created a bash script using 
curl to make the OFX request. Paradoxically it worked while the 
equivalent un-beautified GnuCash request failed.


After little debugging, the key lines in the GnuCash ofx.log were:

== OFX ==
...
... myuserid
mypassword
...
== OFX ==

The above will work if you add a space either at the end of the 
"...myuserid" line, or before "" in the next line. At 
the GnuCash user interface level that involves adding a trailing space 
to the AqBanking userid for Citi.


For reference, below is the OFX template file I use to feed my 
curl-based script. Eventually GnuCash makes an equivalent request. 
(Again, eliminate the leading spaces before "" and it, too fails.)


== OFX ==
OFXHEADER:100
DATA:OFXSGML
VERSION:103
SECURITY:NONE
ENCODING:USASCII
CHARSET:1252
COMPRESSION:NONE
OLDFILEUID:NONE
NEWFILEUID:$OFX_DATETIME




$OFX_DATETIME
$OFX_USER
$OFX_PW
ENG

$OFX_ORG
$OFX_FID

QWIN
2400




$OFX_DATETIME
1


$OFX_ACCOUNT


$OFX_STARTDATE
$OFX_ENDDATE
Y





== OFX ==

If GnuCash did prettified SGML it would avoid this problem with Citi's 
parsing.


  Jim

___
gnucash-user mailing list
gnucash-user@gnucash.org
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
If you are using Nabble or Gmane, please see 
https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
-
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.

Re: [GNC] AqBanking help for Citi CC

2018-06-16 Thread John Ralls
We didn’t change the Bayesian matching itself, sadly. What’s different is that 
the account matches are now recorded as GUIDs instead of name-strings, so 
matches won’t get broken if you change the separator or rename an account.

Regards,
John Ralls


> On Jun 15, 2018, at 7:27 PM, David Carlson  
> wrote:
> 
> I think that the Bayes matching is the same  for both methods.   It is
> supposed to be improved in the 3.x releases, but incompatible with the
> older releases.
> 
> I have not migrated yet, so I have not seen the improved matching.
> 
> David C
> 
> On Fri, Jun 15, 2018, 4:43 PM Evan Van Dyke  wrote:
> 
>> PS: I think you misread… I was wondering if the QFX importer had good
>> baysean matching, the way the OFX online importer does.  If I can’t import
>> my Citi account via OFX, then I’ll be down to manual file imports
>> (unfortunately).
>> 
>> —Evan
>> 
>> On Jun 15, 2018, at 4:39 PM, Evan Van Dyke  wrote:
>> 
>> Yep.  I meant Bayes matching of course.
>> 
>> Sent from my iPhone
>> 
>> On Jun 15, 2018, at 4:36 PM, David Carlson 
>> wrote:
>> 
>> Bales matching?
>> 
>> Is this AI spell checking?
>> 
>> The OFX importer has extensive matching capability, but it is not very
>> user friendly.
>> 
>> David C
>> 
>> On Fri, Jun 15, 2018, 4:24 PM Evan Van Dyke  wrote:
>> 
>>> Ugh, that stinks.
>>> 
>>> Can you get bales matching during QFX import like with online import?
>>> 
 On Jun 15, 2018, at 3:42 PM, Fross, Michael  wrote:
 
 Hi.  I, too have had this issue.  I believe on May 1st Citi has stopped
>>> supporting this service for their credit cards much like they did for bank
>>> accounts in 2015.
 
 I've been forced to download the QFX file and import it.  It works, but
>>> it much more of a pain, especially if you have a lot of accounts.  If you
>>> figure out how to make it work please post it!
 
 Michael
 
 On Fri, Jun 15, 2018 at 12:35 PM, Evan Van Dyke >> > wrote:
 I’ve been using aqBanking to download a number of accounts for the last
>>> few years.  I’ve been unable to download my Citi credit-card since about
>>> early April of this year.   I’ve played around with a couple things
>>> (passwords with no symbols, etc.) but I still can’t manage to make it work.
 
 In the aqBanking wizard if I try to get an account list, nothing is
>>> returned
 If I try to download the account info as normal, the error log says
>>> "403-Forbidden”
 
 I can download other accounts just fine; this one is the only issue I
>>> have.  And it used to work just fine… guessing something changed on Citi’s
>>> end.  Any ideas/help on this one?   I tried google but couldn’t find
>>> anything obvious.
 
 —Evan
 ___
 gnucash-user mailing list
 gnucash-user@gnucash.org 
 To update your subscription preferences or to unsubscribe:
 https://lists.gnucash.org/mailman/listinfo/gnucash-user <
>>> https://lists.gnucash.org/mailman/listinfo/gnucash-user>
 If you are using Nabble or Gmane, please see
>>> https://wiki.gnucash.org/wiki/Mailing_Lists <
>>> https://wiki.gnucash.org/wiki/Mailing_Lists> for more information.
 -
 Please remember to CC this list on all your replies.
 You can do this by using Reply-To-List or Reply-All.
 
>>> 
>>> ___
>>> gnucash-user mailing list
>>> gnucash-user@gnucash.org
>>> To update your subscription preferences or to unsubscribe:
>>> https://lists.gnucash.org/mailman/listinfo/gnucash-user
>>> If you are using Nabble or Gmane, please see
>>> https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
>>> -
>>> Please remember to CC this list on all your replies.
>>> You can do this by using Reply-To-List or Reply-All.
>> 
>> 
>> 
> ___
> gnucash-user mailing list
> gnucash-user@gnucash.org
> To update your subscription preferences or to unsubscribe:
> https://lists.gnucash.org/mailman/listinfo/gnucash-user
> If you are using Nabble or Gmane, please see 
> https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
> -
> Please remember to CC this list on all your replies.
> You can do this by using Reply-To-List or Reply-All.

___
gnucash-user mailing list
gnucash-user@gnucash.org
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
If you are using Nabble or Gmane, please see 
https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
-
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.

Re: [GNC] AqBanking help for Citi CC

2018-06-15 Thread Evan Van Dyke
Great!  I’ll give that a try next month; I just finished reconciling this month 
by hand (ugh).

—Evan

> On Jun 15, 2018, at 9:56 PM, John Ralls  wrote:
> 
> There’s a reason the menu says “Import OFX/QFX...”. They’re the same format, 
> Intuit just fuddled the name to create an excuse to charge licensing fees to 
> banks. GnuCash has no interest in that nonsense so we use the same code to 
> import either.
> 
> Regards,
> John Ralls
> 
> 
>> On Jun 15, 2018, at 2:43 PM, Evan Van Dyke  wrote:
>> 
>> PS: I think you misread… I was wondering if the QFX importer had good 
>> baysean matching, the way the OFX online importer does.  If I can’t import 
>> my Citi account via OFX, then I’ll be down to manual file imports 
>> (unfortunately).
>> 
>> —Evan
>> 
>>> On Jun 15, 2018, at 4:39 PM, Evan Van Dyke  wrote:
>>> 
>>> Yep.  I meant Bayes matching of course.
>>> 
>>> Sent from my iPhone
>>> 
>>> On Jun 15, 2018, at 4:36 PM, David Carlson >> > wrote:
>>> 
 Bales matching? 
 
 Is this AI spell checking?
 
 The OFX importer has extensive matching capability, but it is not very 
 user friendly. 
 
 David C  
 
 On Fri, Jun 15, 2018, 4:24 PM Evan Van Dyke >>> > wrote:
 Ugh, that stinks.
 
 Can you get bales matching during QFX import like with online import?
 
> On Jun 15, 2018, at 3:42 PM, Fross, Michael  > wrote:
> 
> Hi.  I, too have had this issue.  I believe on May 1st Citi has stopped 
> supporting this service for their credit cards much like they did for 
> bank accounts in 2015.
> 
> I've been forced to download the QFX file and import it.  It works, but 
> it much more of a pain, especially if you have a lot of accounts.  If you 
> figure out how to make it work please post it!
> 
> Michael
> 
> On Fri, Jun 15, 2018 at 12:35 PM, Evan Van Dyke    >> wrote:
> I’ve been using aqBanking to download a number of accounts for the last 
> few years.  I’ve been unable to download my Citi credit-card since about 
> early April of this year.   I’ve played around with a couple things 
> (passwords with no symbols, etc.) but I still can’t manage to make it 
> work.
> 
> In the aqBanking wizard if I try to get an account list, nothing is 
> returned
> If I try to download the account info as normal, the error log says 
> "403-Forbidden”
> 
> I can download other accounts just fine; this one is the only issue I 
> have.  And it used to work just fine… guessing something changed on 
> Citi’s end.  Any ideas/help on this one?   I tried google but couldn’t 
> find anything obvious.
> 
> —Evan
> ___
> gnucash-user mailing list
> gnucash-user@gnucash.org  
> >
> To update your subscription preferences or to unsubscribe:
> https://lists.gnucash.org/mailman/listinfo/gnucash-user 
>  
>  >
> If you are using Nabble or Gmane, please see 
> https://wiki.gnucash.org/wiki/Mailing_Lists 
>  
>  > for more information.
> -
> Please remember to CC this list on all your replies.
> You can do this by using Reply-To-List or Reply-All.
> 
 
 ___
 gnucash-user mailing list
 gnucash-user@gnucash.org 
 To update your subscription preferences or to unsubscribe:
 https://lists.gnucash.org/mailman/listinfo/gnucash-user 
 
 If you are using Nabble or Gmane, please see 
 https://wiki.gnucash.org/wiki/Mailing_Lists 
  for more information.
 -
 Please remember to CC this list on all your replies.
 You can do this by using Reply-To-List or Reply-All.
>> 
>> ___
>> gnucash-user mailing list
>> gnucash-user@gnucash.org
>> To update your subscription preferences or to unsubscribe:
>> https://lists.gnucash.org/mailman/listinfo/gnucash-user
>> If you are using Nabble or Gmane, please see 
>> https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
>> -
>> Please remember to CC this list on all your replies.
>> You can do this by using Reply-To-List or Reply-All.
> 


Re: [GNC] AqBanking help for Citi CC

2018-06-15 Thread John Ralls
There’s a reason the menu says “Import OFX/QFX...”. They’re the same format, 
Intuit just fuddled the name to create an excuse to charge licensing fees to 
banks. GnuCash has no interest in that nonsense so we use the same code to 
import either.

Regards,
John Ralls


> On Jun 15, 2018, at 2:43 PM, Evan Van Dyke  wrote:
> 
> PS: I think you misread… I was wondering if the QFX importer had good baysean 
> matching, the way the OFX online importer does.  If I can’t import my Citi 
> account via OFX, then I’ll be down to manual file imports (unfortunately).
> 
> —Evan
> 
>> On Jun 15, 2018, at 4:39 PM, Evan Van Dyke  wrote:
>> 
>> Yep.  I meant Bayes matching of course.
>> 
>> Sent from my iPhone
>> 
>> On Jun 15, 2018, at 4:36 PM, David Carlson > > wrote:
>> 
>>> Bales matching? 
>>> 
>>> Is this AI spell checking?
>>> 
>>> The OFX importer has extensive matching capability, but it is not very user 
>>> friendly. 
>>> 
>>> David C  
>>> 
>>> On Fri, Jun 15, 2018, 4:24 PM Evan Van Dyke >> > wrote:
>>> Ugh, that stinks.
>>> 
>>> Can you get bales matching during QFX import like with online import?
>>> 
 On Jun 15, 2018, at 3:42 PM, Fross, Michael >>> > wrote:
 
 Hi.  I, too have had this issue.  I believe on May 1st Citi has stopped 
 supporting this service for their credit cards much like they did for bank 
 accounts in 2015.
 
 I've been forced to download the QFX file and import it.  It works, but it 
 much more of a pain, especially if you have a lot of accounts.  If you 
 figure out how to make it work please post it!
 
 Michael
 
 On Fri, Jun 15, 2018 at 12:35 PM, Evan Van Dyke >>>  >> wrote:
 I’ve been using aqBanking to download a number of accounts for the last 
 few years.  I’ve been unable to download my Citi credit-card since about 
 early April of this year.   I’ve played around with a couple things 
 (passwords with no symbols, etc.) but I still can’t manage to make it work.
 
 In the aqBanking wizard if I try to get an account list, nothing is 
 returned
 If I try to download the account info as normal, the error log says 
 "403-Forbidden”
 
 I can download other accounts just fine; this one is the only issue I 
 have.  And it used to work just fine… guessing something changed on Citi’s 
 end.  Any ideas/help on this one?   I tried google but couldn’t find 
 anything obvious.
 
 —Evan
 ___
 gnucash-user mailing list
 gnucash-user@gnucash.org  
 >
 To update your subscription preferences or to unsubscribe:
 https://lists.gnucash.org/mailman/listinfo/gnucash-user 
  
 >
 If you are using Nabble or Gmane, please see 
 https://wiki.gnucash.org/wiki/Mailing_Lists 
  
 > for more information.
 -
 Please remember to CC this list on all your replies.
 You can do this by using Reply-To-List or Reply-All.
 
>>> 
>>> ___
>>> gnucash-user mailing list
>>> gnucash-user@gnucash.org 
>>> To update your subscription preferences or to unsubscribe:
>>> https://lists.gnucash.org/mailman/listinfo/gnucash-user 
>>> 
>>> If you are using Nabble or Gmane, please see 
>>> https://wiki.gnucash.org/wiki/Mailing_Lists 
>>>  for more information.
>>> -
>>> Please remember to CC this list on all your replies.
>>> You can do this by using Reply-To-List or Reply-All.
> 
> ___
> gnucash-user mailing list
> gnucash-user@gnucash.org
> To update your subscription preferences or to unsubscribe:
> https://lists.gnucash.org/mailman/listinfo/gnucash-user
> If you are using Nabble or Gmane, please see 
> https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
> -
> Please remember to CC this list on all your replies.
> You can do this by using Reply-To-List or Reply-All.

___
gnucash-user mailing list
gnucash-user@gnucash.org
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
If you are using Nabble or Gmane, please see 
https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
-

Re: [GNC] AqBanking help for Citi CC

2018-06-15 Thread David Carlson
I think that the Bayes matching is the same  for both methods.   It is
supposed to be improved in the 3.x releases, but incompatible with the
older releases.

I have not migrated yet, so I have not seen the improved matching.

David C

On Fri, Jun 15, 2018, 4:43 PM Evan Van Dyke  wrote:

> PS: I think you misread… I was wondering if the QFX importer had good
> baysean matching, the way the OFX online importer does.  If I can’t import
> my Citi account via OFX, then I’ll be down to manual file imports
> (unfortunately).
>
> —Evan
>
> On Jun 15, 2018, at 4:39 PM, Evan Van Dyke  wrote:
>
> Yep.  I meant Bayes matching of course.
>
> Sent from my iPhone
>
> On Jun 15, 2018, at 4:36 PM, David Carlson 
> wrote:
>
> Bales matching?
>
> Is this AI spell checking?
>
> The OFX importer has extensive matching capability, but it is not very
> user friendly.
>
> David C
>
> On Fri, Jun 15, 2018, 4:24 PM Evan Van Dyke  wrote:
>
>> Ugh, that stinks.
>>
>> Can you get bales matching during QFX import like with online import?
>>
>> > On Jun 15, 2018, at 3:42 PM, Fross, Michael  wrote:
>> >
>> > Hi.  I, too have had this issue.  I believe on May 1st Citi has stopped
>> supporting this service for their credit cards much like they did for bank
>> accounts in 2015.
>> >
>> > I've been forced to download the QFX file and import it.  It works, but
>> it much more of a pain, especially if you have a lot of accounts.  If you
>> figure out how to make it work please post it!
>> >
>> > Michael
>> >
>> > On Fri, Jun 15, 2018 at 12:35 PM, Evan Van Dyke > > wrote:
>> > I’ve been using aqBanking to download a number of accounts for the last
>> few years.  I’ve been unable to download my Citi credit-card since about
>> early April of this year.   I’ve played around with a couple things
>> (passwords with no symbols, etc.) but I still can’t manage to make it work.
>> >
>> > In the aqBanking wizard if I try to get an account list, nothing is
>> returned
>> > If I try to download the account info as normal, the error log says
>> "403-Forbidden”
>> >
>> > I can download other accounts just fine; this one is the only issue I
>> have.  And it used to work just fine… guessing something changed on Citi’s
>> end.  Any ideas/help on this one?   I tried google but couldn’t find
>> anything obvious.
>> >
>> > —Evan
>> > ___
>> > gnucash-user mailing list
>> > gnucash-user@gnucash.org 
>> > To update your subscription preferences or to unsubscribe:
>> > https://lists.gnucash.org/mailman/listinfo/gnucash-user <
>> https://lists.gnucash.org/mailman/listinfo/gnucash-user>
>> > If you are using Nabble or Gmane, please see
>> https://wiki.gnucash.org/wiki/Mailing_Lists <
>> https://wiki.gnucash.org/wiki/Mailing_Lists> for more information.
>> > -
>> > Please remember to CC this list on all your replies.
>> > You can do this by using Reply-To-List or Reply-All.
>> >
>>
>> ___
>> gnucash-user mailing list
>> gnucash-user@gnucash.org
>> To update your subscription preferences or to unsubscribe:
>> https://lists.gnucash.org/mailman/listinfo/gnucash-user
>> If you are using Nabble or Gmane, please see
>> https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
>> -
>> Please remember to CC this list on all your replies.
>> You can do this by using Reply-To-List or Reply-All.
>
>
>
___
gnucash-user mailing list
gnucash-user@gnucash.org
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
If you are using Nabble or Gmane, please see 
https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
-
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.

Re: [GNC] AqBanking help for Citi CC

2018-06-15 Thread Evan Van Dyke
PS: I think you misread… I was wondering if the QFX importer had good baysean 
matching, the way the OFX online importer does.  If I can’t import my Citi 
account via OFX, then I’ll be down to manual file imports (unfortunately).

—Evan

> On Jun 15, 2018, at 4:39 PM, Evan Van Dyke  wrote:
> 
> Yep.  I meant Bayes matching of course.
> 
> Sent from my iPhone
> 
> On Jun 15, 2018, at 4:36 PM, David Carlson  > wrote:
> 
>> Bales matching? 
>> 
>> Is this AI spell checking?
>> 
>> The OFX importer has extensive matching capability, but it is not very user 
>> friendly. 
>> 
>> David C  
>> 
>> On Fri, Jun 15, 2018, 4:24 PM Evan Van Dyke > > wrote:
>> Ugh, that stinks.
>> 
>> Can you get bales matching during QFX import like with online import?
>> 
>> > On Jun 15, 2018, at 3:42 PM, Fross, Michael > > > wrote:
>> > 
>> > Hi.  I, too have had this issue.  I believe on May 1st Citi has stopped 
>> > supporting this service for their credit cards much like they did for bank 
>> > accounts in 2015.
>> > 
>> > I've been forced to download the QFX file and import it.  It works, but it 
>> > much more of a pain, especially if you have a lot of accounts.  If you 
>> > figure out how to make it work please post it!
>> > 
>> > Michael
>> > 
>> > On Fri, Jun 15, 2018 at 12:35 PM, Evan Van Dyke > >  > > >> wrote:
>> > I’ve been using aqBanking to download a number of accounts for the last 
>> > few years.  I’ve been unable to download my Citi credit-card since about 
>> > early April of this year.   I’ve played around with a couple things 
>> > (passwords with no symbols, etc.) but I still can’t manage to make it work.
>> > 
>> > In the aqBanking wizard if I try to get an account list, nothing is 
>> > returned
>> > If I try to download the account info as normal, the error log says 
>> > "403-Forbidden”
>> > 
>> > I can download other accounts just fine; this one is the only issue I 
>> > have.  And it used to work just fine… guessing something changed on Citi’s 
>> > end.  Any ideas/help on this one?   I tried google but couldn’t find 
>> > anything obvious.
>> > 
>> > —Evan
>> > ___
>> > gnucash-user mailing list
>> > gnucash-user@gnucash.org  
>> > >
>> > To update your subscription preferences or to unsubscribe:
>> > https://lists.gnucash.org/mailman/listinfo/gnucash-user 
>> >  
>> > > > >
>> > If you are using Nabble or Gmane, please see 
>> > https://wiki.gnucash.org/wiki/Mailing_Lists 
>> >  
>> > > > > for more information.
>> > -
>> > Please remember to CC this list on all your replies.
>> > You can do this by using Reply-To-List or Reply-All.
>> > 
>> 
>> ___
>> gnucash-user mailing list
>> gnucash-user@gnucash.org 
>> To update your subscription preferences or to unsubscribe:
>> https://lists.gnucash.org/mailman/listinfo/gnucash-user 
>> 
>> If you are using Nabble or Gmane, please see 
>> https://wiki.gnucash.org/wiki/Mailing_Lists 
>>  for more information.
>> -
>> Please remember to CC this list on all your replies.
>> You can do this by using Reply-To-List or Reply-All.

___
gnucash-user mailing list
gnucash-user@gnucash.org
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
If you are using Nabble or Gmane, please see 
https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
-
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.

Re: [GNC] AqBanking help for Citi CC

2018-06-15 Thread Evan Van Dyke
Ugh, that stinks.

Can you get bales matching during QFX import like with online import?

> On Jun 15, 2018, at 3:42 PM, Fross, Michael  wrote:
> 
> Hi.  I, too have had this issue.  I believe on May 1st Citi has stopped 
> supporting this service for their credit cards much like they did for bank 
> accounts in 2015.
> 
> I've been forced to download the QFX file and import it.  It works, but it 
> much more of a pain, especially if you have a lot of accounts.  If you figure 
> out how to make it work please post it!
> 
> Michael
> 
> On Fri, Jun 15, 2018 at 12:35 PM, Evan Van Dyke  > wrote:
> I’ve been using aqBanking to download a number of accounts for the last few 
> years.  I’ve been unable to download my Citi credit-card since about early 
> April of this year.   I’ve played around with a couple things (passwords with 
> no symbols, etc.) but I still can’t manage to make it work.
> 
> In the aqBanking wizard if I try to get an account list, nothing is returned
> If I try to download the account info as normal, the error log says 
> "403-Forbidden”
> 
> I can download other accounts just fine; this one is the only issue I have.  
> And it used to work just fine… guessing something changed on Citi’s end.  Any 
> ideas/help on this one?   I tried google but couldn’t find anything obvious.
> 
> —Evan
> ___
> gnucash-user mailing list
> gnucash-user@gnucash.org 
> To update your subscription preferences or to unsubscribe:
> https://lists.gnucash.org/mailman/listinfo/gnucash-user 
> 
> If you are using Nabble or Gmane, please see 
> https://wiki.gnucash.org/wiki/Mailing_Lists 
>  for more information.
> -
> Please remember to CC this list on all your replies.
> You can do this by using Reply-To-List or Reply-All.
> 

___
gnucash-user mailing list
gnucash-user@gnucash.org
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
If you are using Nabble or Gmane, please see 
https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
-
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.

Re: [GNC] AqBanking help for Citi CC

2018-06-15 Thread Fross, Michael
Hi.  I, too have had this issue.  I believe on May 1st Citi has stopped
supporting this service for their credit cards much like they did for bank
accounts in 2015.

I've been forced to download the QFX file and import it.  It works, but it
much more of a pain, especially if you have a lot of accounts.  If you
figure out how to make it work please post it!

Michael

On Fri, Jun 15, 2018 at 12:35 PM, Evan Van Dyke  wrote:

> I’ve been using aqBanking to download a number of accounts for the last
> few years.  I’ve been unable to download my Citi credit-card since about
> early April of this year.   I’ve played around with a couple things
> (passwords with no symbols, etc.) but I still can’t manage to make it work.
>
> In the aqBanking wizard if I try to get an account list, nothing is
> returned
> If I try to download the account info as normal, the error log says
> "403-Forbidden”
>
> I can download other accounts just fine; this one is the only issue I
> have.  And it used to work just fine… guessing something changed on Citi’s
> end.  Any ideas/help on this one?   I tried google but couldn’t find
> anything obvious.
>
> —Evan
> ___
> gnucash-user mailing list
> gnucash-user@gnucash.org
> To update your subscription preferences or to unsubscribe:
> https://lists.gnucash.org/mailman/listinfo/gnucash-user
> If you are using Nabble or Gmane, please see
> https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
> -
> Please remember to CC this list on all your replies.
> You can do this by using Reply-To-List or Reply-All.
___
gnucash-user mailing list
gnucash-user@gnucash.org
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
If you are using Nabble or Gmane, please see 
https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
-
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.