You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to magellan-acti...@googlegroups.com
There was mention that OAuth is a ways off, so what is the current user authentication mechanism to be able to validate the user and get permission to access their information?
Some of the calls take an access_token which I'm guessing is a user access token to grab their data, but I didn't see mention of how to acquire the access_token in the api docs.
Anthony Pelosi
unread,
Sep 13, 2012, 5:37:26 PM9/13/12
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to magellan-acti...@googlegroups.com
Harry,
Good question. Cloudmade used some internal web services we have for authenticating with the Magellan GPS user accounts to get the access_token when building the Magellan Active website. But we obviously need to produce a wrapper around those authentication services for 3rd party developers using the Magellan Active web services. Those internal web services for Magellan GPS user account authentication require username and password and return the access_token. So the user will have to provide you with their Magellan GPS username (email) and password in order for you to get their access_token. It looks like the username and password is passed as clear text in the xml request for that web service.