Skip to content
This repository has been archived by the owner on Aug 13, 2019. It is now read-only.

Missing authorization code: After changing admin password and revoking access #10

Open
DannyHernandez opened this issue Feb 23, 2015 · 3 comments

Comments

@DannyHernandez
Copy link

I was consistently getting the error below. It started right after I changed the password on the admin account and restarted prod (running in docker). I did not get this error locally after changing the password... I checked and my google app twitch-gaps doesn't have offline permission from my gmail account. I tried revoking access and now I pretty expectedly get the same missing authorization code. I think the quickest fix on my end would be for me to delete existing credentials. Where are they stored?

[2015-02-21 03:04:34.719315] [1] Refreshing expired token: user=""
== Sinatra has ended his set (crowd applauds)
/gaps/vendor/bundle/ruby/2.1.0/gems/signet-0.5.1/lib/signet/oauth_2/client.rb:906:in generate_access_token_request': Missing authorization code. (raised from thread pool) (ArgumentError) from /gaps/vendor/bundle/ruby/2.1.0/gems/signet-0.5.1/lib/signet/oauth_2/client.rb:930:infetch_access_token'
from /gaps/vendor/bundle/ruby/2.1.0/gems/signet-0.5.1/lib/signet/oauth_2/client.rb:956:in fetch_access_token!' from /gaps/lib/gaps/db/user.rb:241:indo_refresh'
from /gaps/lib/gaps/db/user.rb:101:in client' from /gaps/lib/gaps/requestor.rb:131:inlister_client'
from /gaps/lib/gaps/requestor.rb:141:in get_client' from /gaps/lib/gaps/requestor.rb:155:inrequest'
from /gaps/lib/gaps/requestor.rb:193:in block in request_all' from /gaps/vendor/bundle/ruby/2.1.0/gems/activesupport-4.1.8/lib/active_support/core_ext/range/each.rb:7:ineach'
from /gaps/vendor/bundle/ruby/2.1.0/gems/activesupport-4.1.8/lib/active_support/core_ext/range/each.rb:7:in each_with_time_with_zone' from /gaps/lib/gaps/requestor.rb:189:inrequest_all'
from /gaps/lib/gaps/requestor.rb:68:in membership_list' from /gaps/lib/gaps/requestor.rb:58:inblock in membership_list_for_group'
from /gaps/lib/gaps/db/cache.rb:68:in call' from /gaps/lib/gaps/db/cache.rb:68:inblock in cache_lookup'
from /gaps/vendor/bundle/ruby/2.1.0/gems/thread-0.1.4/lib/thread/pool.rb:56:in call' from /gaps/vendor/bundle/ruby/2.1.0/gems/thread-0.1.4/lib/thread/pool.rb:56:inexecute'
from /gaps/vendor/bundle/ruby/2.1.0/gems/thread-0.1.4/lib/thread/pool.rb:384:in block (2 levels) in spawn_thread' from /gaps/vendor/bundle/ruby/2.1.0/gems/thread-0.1.4/lib/thread/pool.rb:351:inloop'
from /gaps/vendor/bundle/ruby/2.1.0/gems/thread-0.1.4/lib/thread/pool.rb:351:in block in spawn_thread' from /gaps/vendor/bundle/ruby/2.1.0/gems/logging-1.8.2/lib/logging/diagnostic_context.rb:323:incall'
from /gaps/vendor/bundle/ruby/2.1.0/gems/logging-1.8.2/lib/logging/diagnostic_context.rb:323:in `block in create_with_logging_context'

@DannyHernandez
Copy link
Author

I fixed my issue by removing the admin user from Mongo

db.user.remove({name: "Danny Hernandez"})

@gdb
Copy link
Contributor

gdb commented Feb 27, 2015

Ah, whoops, sorry for dropping this. Going to leave this issue open so we fix the underlying issue, but glad you were able to work around it.

@DannyHernandez
Copy link
Author

No worries.

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

No branches or pull requests

2 participants