Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Api url has changed

See original GitHub issue

I’ve been using this lib for a couple months, with everything ok. Now I’m getting this error:

FetchError: request to https://prod-auth.nubank.com.br/api/token failed, reason: write EPROTO 140736572793792:error:14094412:SSL routines:ssl3_read_bytes:sslv3 alert bad certificate:../deps/openssl/openssl/ssl/s3_ pkt.c:1498:SSL alert number 42 140736572793792:error:1409E0E5:SSL routines:ssl3_write_bytes:ssl handshake failure:../deps/openssl/openssl/ssl/s3_pkt.c:659

I think the api URL has changed to this new url:

https://prod-s0-webapp-proxy.nubank.com.br/api/proxy/AJxL5LBUC2Tx4PB-W6VD1SEIOd2xp14EDQ.aHR0cHM6Ly9wcm9kLWdsb2JhbC1hdXRoLm51YmFuay5jb20uYnIvYXBpL3Rva2Vu

Issue Analytics

State:
Created 5 years ago
Reactions:4
Comments:19 (5 by maintainers)

Top GitHub Comments

3reactions

dygufacommented, Jun 10, 2019

@danilobarion1986 are you considering the qrcode step required to get the “events link”? I’m also trying to use nubank’s api to get my purchase list but from what I’m seeing I will have to use: i) discovery links; ii) login link; iii) lift link (which involves reading a qrcode); iv) and finally events link. Do you have a different approach on mind?

Yes, this is the exact workflow to authenticate. As I said before, I won’t be able to make a PR with the javascript code, but I finish my ruby automation (it can be viewed here). Before I made it I tried to use a python automation, but I encounter some errors with it and then decided to roll out my own.

Thanks! I’m already finishing an implementation using Javascript following the workflow described above, however, I’m not sure if it fits this api considering it would be a huge breaking change this new qrcode requirement. It only makes sense in a major release (or maybe not considering it’s already broken).

2reactions

danilobarion1986commented, Jun 10, 2019

Cool @dygufa ! I think that fix the dynamic URI issue and add other login flow, considering QR Code validation, are two different things (If someone is already using login without QR Code, what I don’t know if it is possible…).

But if everybody needs a QR Code to log in them I agree with you that is better to launch a new breaking version and deprecate this one