New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't auth #16
Comments
Looks like they changed the API on us, I'm getting auth errors now too.. I'm looking into this. |
The API was changed with new Android app release. The old Android apps do not work too ;) |
Gah, that sucks.. Let me see what I can find out.. |
I’m guessing this is because of the negative press that Ring recently
received about formerly authorized people still being able to access the
camera feeds even after the account password was changed. E.g. the person
that was spying on their ex’s Ring cameras.
I knew about this “issue” for over a year, but I suppose it took the
mainstream media’s spotlight to make Ring suddenly care.
On Thu, May 31, 2018 at 8:45 AM Dav Glass ***@***.***> wrote:
Gah, that sucks.. Let me see what I can find out..
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#16 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAnfLu3vvmXVheK3Xj3BccYqn6iG_jRLks5t3-XMgaJpZM4UUbrW>
.
--
Sent from Gmail Mobile --rnr--
|
The auth tokens expiring after some time, and you have to know the new password to be able to get the new token. Sounds like bulshit. BTW: mitmproxy do not work in a dumb way anymore - they started using certificate pinning |
I just tested the |
Reversed Android app - they switched to oauth protocol. Stay tuned ... |
sneaky but nice to see they are finally taking security a little more
seriously
…On Thu, May 31, 2018 at 2:45 PM, Rus ***@***.***> wrote:
Reversed Android app - they switched to oauth protocol. Stay tuned ...
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#16 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ACzdQEHhwpb219wG4xnuX_peG56umOSiks5t3_PngaJpZM4UUbrW>
.
--
Angelo
|
No ;) In short:
you will have the json reply with "access_token"
but set the authorization header to "bearer " + access_token. You will have usual profile object reply. Next work as usual |
Oh nice! Trying this now.. |
Pushed up |
Could someone describe a solution to this problem than an ordinary guy can follow? |
@tommh44 |
The text was updated successfully, but these errors were encountered: