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
A few pieces of the docs refer to an "auth_token" and not an "access-token".... and, for example, validate_token says it expects only the token and uid. Is this the case? I couldn't get it to work unless I had "access-token", "uid", and "client." I'd be more than happy to make a PR to update the readme but I want to double-check if this is the case or I may have missed something.
Thanks!
The text was updated successfully, but these errors were encountered:
I think "auth_token" means "access-token, uid and client". Not sure but
anyway, you should always send access-token, uid and client when you need
to get logged.
On Wed, May 13, 2015 at 11:02 AM Matthew Herz [email protected]
wrote:
A few pieces of the docs refer to an "auth_token" and not an
"access-token".... and, for example, validate_token says it expects only
the token and uid. Is this the case? I couldn't get it to work unless I had
"access-token", "uid", and "client." I'd be more than happy to make a PR to
update the readme but I want to double-check if this is the case or I may
have missed something.
Thanks!
—
Reply to this email directly or view it on GitHub #243.
A few pieces of the docs refer to an "auth_token" and not an "access-token".... and, for example, validate_token says it expects only the token and uid. Is this the case? I couldn't get it to work unless I had "access-token", "uid", and "client." I'd be more than happy to make a PR to update the readme but I want to double-check if this is the case or I may have missed something.
Thanks!
The text was updated successfully, but these errors were encountered: