Introducing TAuth: Why OAuth 2.0 is bad for banking APIs and how we're fixing it

Re:Introducing TAuth: Why OAuth 2.0 is bad for banking APIs ... by JDDunn9 on Thursday May 05, 2016 @12:48PM (#11637700)

I visited the homepage (https://www.teller.io/) and got a warning about the SSL cert being invalid. Kind of ironic. :)

[ Parent | on HN ]

Re:Introducing TAuth: Why OAuth 2.0 is bad for banking APIs ... by Freak_NL on Thursday May 05, 2016 @01:07PM (#11637899)

https://teller.io seems fine though. Still sloppy.

[ Parent | on HN ]

Re:Introducing TAuth: Why OAuth 2.0 is bad for banking APIs ... by levemi on Thursday May 05, 2016 @01:03PM (#11637859)

> I visited the homepage (https://www.teller.io/) and got a warning about the SSL cert being invalid. Kind of ironic. :)

The correct URL is https://teller.io and then you wont get an SSL cert warning. Not everyone uses "www". Nowhere on teller.io do you see a link to www. You put garbage in and got garbage out.

[ Parent | on HN ]

Re:Introducing TAuth: Why OAuth 2.0 is bad for banking APIs ... by amgreg on Thursday May 05, 2016 @03:36PM (#11639085)

many if not most people input the www subdomain by rote. unless teller does not care about that category of people, it should probably fix the issue

[ Parent | on HN ]

Re:Introducing TAuth: Why OAuth 2.0 is bad for banking APIs ... by mderazon on Thursday May 05, 2016 @04:31PM (#11639448)

Of course they should. Redirect traffic from www.teller.io to teller.io

[ Parent | on HN ]

Re:Introducing TAuth: Why OAuth 2.0 is bad for banking APIs ... by anaptdemise on Thursday May 05, 2016 @05:57PM (#11639951)

Or, correctly teller.io to www.teller.io. Previous discussion https://news.ycombinator.com/item?id=11004396

[ Parent | on HN ]