Skip to content
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

Auth permission level changes to SDK #33

Open
sshadmand opened this issue Mar 16, 2012 · 1 comment
Open

Auth permission level changes to SDK #33

sshadmand opened this issue Mar 16, 2012 · 1 comment

Comments

@sshadmand
Copy link
Contributor

Hey SDK team. I noticed that when I gave FB permission to post a comment from the app it only requested the "comment to my wall" level permissions.
If we want to get the friend count of a user that has authed but only to that level won't it limit our ability to do so?

Jason Polites [email protected]

I think this is correct, but I think it's not a no big deal, although we may have to make some changes to the SDK.

If we add new permission, the new SDK will know it's the new SDK and know that any stored user credentials will not have these permissions so it needs to re-auth the user. I know for Android that I don't currently store the actual permissions the user has authorized so I would need to add that.

Twitter permissions are controlled by the developer on the Twitter App via the twitter website, so we also may need to handle this somehow.

@nwg
Copy link
Contributor

nwg commented Mar 17, 2012

We should have a (currently required) reason for any permission we ask for, or people might reject auth altogether. As Jason states, if we do need to upgrade perms in the future we can cleanly reauth.

For Twitter, we currently require twitter read-write, but not direct-message, be configured by the dev for things to work correctly.

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

No branches or pull requests

2 participants