Skip to content
This repository has been archived by the owner on Feb 8, 2018. It is now read-only.

react when user unauthorizes via OAuth provider #823

Closed
mat-0 opened this issue Apr 5, 2013 · 12 comments
Closed

react when user unauthorizes via OAuth provider #823

mat-0 opened this issue Apr 5, 2013 · 12 comments

Comments

@mat-0
Copy link

mat-0 commented Apr 5, 2013

Was: option to delete account, change image and remove accounts when auth denied

  1. added both twitter and github accounts, image persists with github image want twitter image.
  2. removed github permissions from github, image and account persists on gittip.
  3. no option to delete accounts.
  4. no option to delete gittip account either.

thanks

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

@chadwhitacre
Copy link
Contributor

Thanks @kutf! I've added +1s for you to:

Let's keep this ticket for point 2 above.

@chadwhitacre
Copy link
Contributor

+1 from @tarsius in private email.

@Changaco
Copy link
Contributor

We can't because we're not notified of revocations.

@chadwhitacre
Copy link
Contributor

We can't because we're not notified of revocations.

You've confirmed this with Twitter and GitHub?

@Changaco
Copy link
Contributor

You've confirmed this with Twitter and GitHub?

I've looked at the docs, I haven't found any way to get notified of revocations. I don't know any OAuth provider who has webhooks for that.

@chadwhitacre
Copy link
Contributor

Okay. Seems like a wart.

@chadwhitacre
Copy link
Contributor

Somehow Freshdesk is reacting to Facebook revocations:

screen shot 2015-03-09 at 2 42 31 pm

Reopening.

@chadwhitacre chadwhitacre reopened this Mar 9, 2015
@rohitpaulk
Copy link
Contributor

screenshot from 2015-03-10 00 21 34

From https://developers.facebook.com/docs/facebook-login/manually-build-a-login-flow/v2.2

You can enable a deauthorize callback via the App Dashboard. Just go to your app, then choose the Settings menu, and finally the Advanced tab. A text field is provided for the Deauthorize Callback URL.

Whenever a user of your app de-authorizes it, this URL will be sent an HTTP POST containing a signed request. Read our guide to parsing the signed request to see how to decode this to find out the user ID that triggered the callback.

@chadwhitacre
Copy link
Contributor

@sushil1208
Copy link

How can an attacker attack through the report 129209??

@chadwhitacre
Copy link
Contributor

@sushil1208 Sorry, I don't understand. :-( Can you rephrase the question?

@chadwhitacre
Copy link
Contributor

Closing in light of our decision to shut down Gratipay.

Thank you all for a great run, and I'm sorry it didn't work out! 😞 💃

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

5 participants