Bug #1999

[wellsfargo] Website got updated

Added by Oleg Plakhotniuk about 2 years ago. Updated about 2 years ago.

Status:Resolved Start:2015-06-25
Priority:Normal Due date:
Assigned to:Oleg Plakhotniuk % Done:

100%

Category:Modules Spent time: -
Target version:-
Module:wellsfargo Branch:

Description

Welcome good old dynamically-generated obfuscated JavaScript... Burn in hell...


Related issues

duplicated by weboob - Bug #1997: boobank wellsfargo module broken Resolved 2015-06-24

Associated revisions

Revision 337b8278024a1644a9336d71b28e678d7a0ecf34
Added by Oleg Plakhotniuk about 2 years ago

[wellsfargo] Update to new login security checks. Closes #1999

History

Updated by Oleg Plakhotniuk about 2 years ago

  • Status changed from In progress to To merge
  • % Done changed from 50 to 100

Done in branch issue1999

Now the module uses PhantomJS. Sorry about that.

Updated by Oleg Plakhotniuk about 2 years ago

  • Status changed from To merge to In progress
  • % Done changed from 100 to 50

Hold on, now it keeps asking security questions.

Updated by Oleg Plakhotniuk about 2 years ago

  • Status changed from In progress to To merge
  • % Done changed from 50 to 100

Ok, we're good to go. I added security questions and answers to the config.

Updated by grant tzabro about 2 years ago

Hi Oleg -

In which branch is this fixed? I don't see any branches in the symlink.me repo.

Updated by Oleg Plakhotniuk about 2 years ago

Grant, the fix is in the branch issue1999 of my personal repo: git.symlink.me/oleg/weboob.git

Updated by Oleg Plakhotniuk about 2 years ago

  • Status changed from To merge to Resolved

Updated by grant tzabro about 2 years ago

figured out the issue:

in wellsfargo/brower.py need to set the ssl-protocol level for phantomjs to TLSv1:

check_output(["phantomjs", "--ssl-protocol=TLSv1", scrn], stderr=STDOUT)

also, didn't need the security questions. in fact, wells fargo is phasing those out, and if you use an account view, then there are no security questions. also, there's no way to view your own security question, let alone the answers.

it does still occasionally fail with these errors:

error: cannot recognize version marker
warning: trying to repair broken xref
warning: ignoring invalid character in hex string
warning: ... repeated 104 times ...
warning: lexical error (unexpected ')')
warning: ... repeated 2 times ...
warning: ignoring invalid character in hex string
warning: ... repeated 33 times ...

but if I try again, it works.

Also available in: Atom PDF