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

goo.gl 403 error #20

Closed
neocotic opened this Issue Jul 27, 2011 · 6 comments

Comments

Projects
None yet
1 participant
@neocotic
Member

neocotic commented Jul 27, 2011

There seems to be an issue with authentication for the goo.gl URL shortener. I believe it might be having problems when the same version is authenticated with multiple machines.

@ghost ghost assigned neocotic Jul 27, 2011

@neocotic

This comment has been minimized.

Show comment
Hide comment
@neocotic

neocotic Jul 28, 2011

Member

I've experimented and this doesn't seem to be related with multiple installations and will need to retest on my Mac as that's the only place I got the error. May need to debug the exact response.

Member

neocotic commented Jul 28, 2011

I've experimented and this doesn't seem to be related with multiple installations and will need to retest on my Mac as that's the only place I got the error. May need to debug the exact response.

@neocotic

This comment has been minimized.

Show comment
Hide comment
@neocotic

neocotic Aug 8, 2011

Member

I found that this problem was with authentication tokens stored in localStorage on my Mac. I believe I revoked access for this from my Google dashboard but I would have thought that this would have resulted in a new authentication process next time I attempted to contact goo.gl. I may need to experiment with this further and may require an option to clear any stored values from localStorage (e.g. Flush Tokens button).

Member

neocotic commented Aug 8, 2011

I found that this problem was with authentication tokens stored in localStorage on my Mac. I believe I revoked access for this from my Google dashboard but I would have thought that this would have resulted in a new authentication process next time I attempted to contact goo.gl. I may need to experiment with this further and may require an option to clear any stored values from localStorage (e.g. Flush Tokens button).

@neocotic

This comment has been minimized.

Show comment
Hide comment
@neocotic

neocotic Jan 16, 2012

Member

Hopefully this should resolve any future problems.

Member

neocotic commented Jan 16, 2012

Hopefully this should resolve any future problems.

@neocotic neocotic closed this Jan 16, 2012

@neocotic neocotic reopened this Feb 10, 2012

@neocotic

This comment has been minimized.

Show comment
Hide comment
@neocotic

neocotic Feb 10, 2012

Member

I want to look at this again to make this slightly cleaner. Instead of directly deleting the values stored in localStorage or checking their existence I could probably use oauth.clearTokens() and oauth.hasToken() respectively. I'll investigate this further. 1.0.0 must be perfect!

Member

neocotic commented Feb 10, 2012

I want to look at this again to make this slightly cleaner. Instead of directly deleting the values stored in localStorage or checking their existence I could probably use oauth.clearTokens() and oauth.hasToken() respectively. I'll investigate this further. 1.0.0 must be perfect!

@neocotic

This comment has been minimized.

Show comment
Hide comment
@neocotic

neocotic Feb 10, 2012

Member

Also, I'm tempted to change the way that this is worded etc.

Instead of having a flush button when the user is authenticated. Add a Login button to the options page that, when clicked, calls oauth.authorize and then changes to a Logout button if it was a success which, when clicked again, will cause the tokens to be cleared and change back to the Login button. This would make callUrlShortener much simpler and the whole process cleaner. Finally, this would mean that OAuth enabled detection would no longer be required and it's just a matter of whether or not we have the tokens. Obviously, the user will be logged out by default (for new installations).

The googlOAuth option could also be deprecated (and maybe replaced with googlAccount) and change its functionality to oauth.hasToken().

Member

neocotic commented Feb 10, 2012

Also, I'm tempted to change the way that this is worded etc.

Instead of having a flush button when the user is authenticated. Add a Login button to the options page that, when clicked, calls oauth.authorize and then changes to a Logout button if it was a success which, when clicked again, will cause the tokens to be cleared and change back to the Login button. This would make callUrlShortener much simpler and the whole process cleaner. Finally, this would mean that OAuth enabled detection would no longer be required and it's just a matter of whether or not we have the tokens. Obviously, the user will be logged out by default (for new installations).

The googlOAuth option could also be deprecated (and maybe replaced with googlAccount) and change its functionality to oauth.hasToken().

neocotic added a commit that referenced this issue Feb 13, 2012

neocotic added a commit that referenced this issue Feb 13, 2012

neocotic added a commit that referenced this issue Feb 13, 2012

@neocotic

This comment has been minimized.

Show comment
Hide comment
@neocotic

neocotic Feb 13, 2012

Member

This feels much more natural now and works great!

Member

neocotic commented Feb 13, 2012

This feels much more natural now and works great!

@neocotic neocotic closed this Feb 13, 2012

@neocotic neocotic added security and removed Error labels Nov 15, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment