Do more on the web, with a fast and secure browser!

Download Opera browser with:

  • built-in ad blocker
  • battery saver
  • free VPN
Download Opera

not able to log in to ING Bank in the Netherlands

  • After years of use, suddenly could no longer log in to ING Bank (in NL).

    After searching, learned the only thing to do was either use another browser (!) or downgrade.

    Downgrading was not difficult, from v. 12.(+) to 11.64. I can now log in again to ING Bank.

    I have friends who have contacted me with the same problem, so I wanted to post it here if it may help anyone else.

    Sonny

    Details: I did edit the index.ini file in the mailbox folder as suggested (in the Forum Topic, link below) and it worked the first time, including my mail and all preferences. (also History, Bookmarks, etc.)

    Forum Topic: "How to downgrade to Opera 11.64 without mail problem"
    http://my.opera.com/community/forums/topic.dml?id=1442132

  • Thank you for your post and the useful link.

    I am also using Opera 11.64 to avoid some problems with Opera 12.16.

    Why I Won't be Upgrading to Opera 12.xx

  • Ask your bank why they ignore support for Opera browser.
    Unfortunately, they likely will say to use Chropera instead of the original Opera browser.

    Also you can try to mask as Firefox(latest one) with no guarantee of getting working online bank page:

    - Close Opera.

    - Edit override.ini (usually in C:\Users\%User_Name%\AppData\Roaming\Opera\Opera\ ):

    Add into the "[Overrides]":
    mijn.ing.nl

    Add into the end file:
    [mijn.ing.nl] section
    the string:
    User Prefs|Custom User-Agent=Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:25.0) Gecko/20100101 Firefox/25.0

    or try to mask as Chrome:

    [mijn.ing.nl]
    User Prefs|Custom User-Agent=Mozilla/5.0 (Windows NT 6.2; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/32.0.1667.0 Safari/537.36

  • Originally posted by STNG:

    Ask your bank why they ignore support for Opera browser.

    Keep in mind that it works with 11.64.

    Originally posted by STNG:

    Also you can try to mask as Firefox(latest one) with no guarantee of getting working online bank page

    Once again, it works with 11.64 so UA is not the problem.

    @dumascon
    I suspect something, hence my question: Did you try with 12.14?

  • Krake

    Keep in mind that it works with 11.64.

    11.64 is an obsolete version with a vanishingly small market share.
    So unlikely an ING's developers ever tested their login page with 11.64.

    Once again, it works with 11.64 so UA is not the problem.

    But it might help(might not!) because of different code provided for a different UA.

  • I had the same problems with the ING site.
    Asked ING in an email if they changed anything at their end, but the could not help me and suggested that I call a payed support number.
    Did not want to do that so tried several things in 12.16 like masking or other tricks and it made no difference.
    Tried Opera 17 quickly and it worked, but I do not like the new version at all.
    Decided to downgraded this weekend and 12.14 is the newest version still working.
    I susspect that somthing has changed in 12.15 and 12.16 but have no idea what it could be...
    I know some people prefer to use the older 11.64, but because we are dealing with a banking site, using 12.14 seems the safer thing to do.

  • This has nothing to do with user agent snooping.
    It seems to be a bug in Opera in the cookie domain handling.

    After entering the correct login credentials, there are a couple of redirects, one of which is a request for the URL
        https://bankieren.mijn.ing.nl/ssm/sso/login?Target=https://bankieren.mijn.ing.nl/particulier/betalen/index
    In the response, the server sets (among others) the following cookies:

        Set-Cookie: agreementid=[snipped]; Domain=.ing.nl; Path=/; Secure
        Set-Cookie: atp=[snipped]; Domain=.ing.nl; Path=/; Secure
    

    This response also includes a redirect:

        HTTP/1.1 302 Moved Temporarily
        location: https://bankieren.mijn.ing.nl/ssm/sso/continue?Target=https%3A%2F%2Fbankieren.mijn.ing.nl%2Fparticulier%2Fbetalen%2Findex
    

    In the next request, the URL
        https://bankieren.mijn.ing.nl/ssm/sso/continue?Target=https%3A%2F%2Fbankieren.mijn.ing.nl%2Fparticulier%2Fbetalen%2Findex
    is requested. However, the two aforementioned cookies are missing here.

    Looking through RFC 6265, I see no reason why these cookies should be omitted.
    And when using Firefox, these cookies are present as expected, and the site is usable.

    If I intercept the request and change the value in the response to 'bankieren.mijn.ing.nl', I can make use of the site in Opera as I used to be able to.
    (As all requests are to bankieren.mijn.ing.nl, the Domain parameter is not even necessary.)

    If I had to make a guess, I'd say that the three periods in the domain name is what's confusing Opera.

    I have not reported the bug via the Opera bug tracker, as the tens of bug reports I've made in the past never seemed to have any effect. But don't let that stop you from trying to report it yourself; maybe it's just me.

  • Looking through RFC 6265, I see no reason why these cookies should be omitted.

    Though section "5.1.3. Domain Matching" mentions the following should hold:

    The string is a host name (i.e., not an IP address).

    ".ing.nl" is -strictly- NOT a hostname. However the intention seems pretty clear from the RFC. Maybe Opera is to strict in that respect?

Locked