Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
producteev-api-discuss
Home
+ new post
About this group
Join this group
Message from discussion Error authenticating user and obtaining token
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Cory Deppen  
View profile  
 More options Sep 16 2012, 3:58 pm
From: Cory Deppen <corydep...@gmail.com>
Date: Sun, 16 Sep 2012 12:58:07 -0700 (PDT)
Local: Sun, Sep 16 2012 3:58 pm
Subject: Re: Error authenticating user and obtaining token
Print | View thread | Show original | Report this message | Find messages by this author

I discovered what I was doing wrong. I thought the api_secret was included
in the signature string like the other params, but it just needs to be
appended to the end of the string prior to creating the MD5 hash. So the
signature string ends up looking
like "api_key[api_key_here]email[email_here]password[password_here][api_secret_h ere]".

On Sunday, September 16, 2012 1:23:42 PM UTC-4, Cory Deppen wrote:

> Just getting the token for a user has been a challenge so far. If I
> understand the API, the signature string should be
> "api_key[api_key_here]email[email_here]password[password_here]" if
> I'm calling users/login. I'm confused, though, since the docs say
> "your_signature is a signature of all the parameters sent to the call.
> Signatures are created by concatenating every scalar argument (ie: non
> array) listed in alphabetical order with your api secret". So should the
> secret be part of the signature string or not, since it's not an argument
> being passed? I've tried including it in the signature string and excluding
> it, but I continue to get a 403 with error "Wrong api_key or signature". So
> it seems my method for getting the signature is wrong or the API key I'm
> using is inactive/invalid. Is there a way of determining if my API key is
> active/valid?

> Also, the docs mention the email and password parameters are integers. Is
> this a typo and they should really be strings?

> I'm really at a loss and would appreciate any guidance. Hopefully I'm
> overlooking something simple.


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2013 Google