-
Notifications
You must be signed in to change notification settings - Fork 31
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
Credentials not being returned from Mailchimp #3
Comments
Sorry for that, i'll have a look as soon as possible. Le 11 juin 2012 à 03:41, Brian Getting a écrit :
|
That's awesome, I appreciate it. I'm hoping it's just something dumb that I am doing… :) On Jun 11, 2012, at 12:35 AM, florian mhun wrote:
|
You are right there is a problem. I ran the example app with sinatra and get the undefined method exception too. I'll debug that, if you find something don't hesitate to keep me informed ;) Thank you very much for your mail Brian. Le 11 juin 2012 à 18:44, Brian Getting a écrit :
|
The json response returned by the MailChimp API not return user_hash key anymore, I fixed that. Check the commit to view the change, it works now. Le 11 juin 2012 à 18:44, Brian Getting a écrit :
|
Are you seeing the credentials (specifically the token) being returned now? On Jun 11, 2012, at 2:51 PM, florian mhun wrote:
|
Yes I do but a part of the token is located in metadata and you need to build it yourself. If you wan't to perform authenticated api calls on Mailchimp you need two things :
Then, your real access token that you put to the authenticated api calls is token-dc as specified in the developer documentation http://apidocs.mailchimp.com/oauth2/#implementation-details Let me know if i answer your question, my english may be hard to understand sometimes ! Le 12 juin 2012 à 00:12, Brian Getting a écrit :
|
Allow passing full_host in options
When I follow the example for this strategy, there are no credentials returned in the omniauth.auth array:
Any ideas? It does spit back all of the user data, which gives me the impression that it is getting a token back since it would need that to get at the user data, right?
Anyway, love that someone built a strategy for Mailchimp, and any help that you can provide in getting this working would be great. I've always connected directly using the Oauth2 gem, but I'm hoping that this will be easier.
Thanks.
The text was updated successfully, but these errors were encountered: