You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My app has some users who need read+write, but the majority just need read, so my login link is: "auth/twitter?x_auth_access_type=read"
For users who need read+write, I use: "auth/twitter?x_auth_access_type=write"
Both work, but if a user who originally logged in with one type of permission tries to login using the other one, twitter hangs with the message "(twitter) Request phase initiated."
Using this link: "auth/twitter?use_authorize=true" makes it work so either type of user can login, but it requires users to re-authorize the app each time they login (as it's supposed to).
Is there a way that users can switch between the two x_auth options without it hanging, or do I just need to require all users to re-authorize the app each time using use_authorize=true for it to work? My goal is for the majority of users to have seamless read only login from homepage, but then to not have it break if a previous read+write user tries that main login on the homepage (they would then click the read+write link from within the app when they need to authorize writes).
The text was updated successfully, but these errors were encountered:
Thanks for making this!
My app has some users who need read+write, but the majority just need read, so my login link is: "auth/twitter?x_auth_access_type=read"
For users who need read+write, I use: "auth/twitter?x_auth_access_type=write"
Both work, but if a user who originally logged in with one type of permission tries to login using the other one, twitter hangs with the message "(twitter) Request phase initiated."
Using this link: "auth/twitter?use_authorize=true" makes it work so either type of user can login, but it requires users to re-authorize the app each time they login (as it's supposed to).
Is there a way that users can switch between the two x_auth options without it hanging, or do I just need to require all users to re-authorize the app each time using use_authorize=true for it to work? My goal is for the majority of users to have seamless read only login from homepage, but then to not have it break if a previous read+write user tries that main login on the homepage (they would then click the read+write link from within the app when they need to authorize writes).
The text was updated successfully, but these errors were encountered: