Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.python > #30120 > unrolled thread

google api and oauth2

Started by"Littlefield, Tyler" <tyler@tysdomain.com>
First post2012-09-25 13:04 -0600
Last post2012-09-25 13:04 -0600
Articles 1 — 1 participant

Back to article view | Back to comp.lang.python


Contents

  google api and oauth2 "Littlefield, Tyler" <tyler@tysdomain.com> - 2012-09-25 13:04 -0600

#30120 — google api and oauth2

From"Littlefield, Tyler" <tyler@tysdomain.com>
Date2012-09-25 13:04 -0600
Subjectgoogle api and oauth2
Message-ID<mailman.1368.1348599885.27098.python-list@python.org>
Hello all:
I've been trying  to figure out the oauth2client part of google's api, 
and I am really confused.
It shows a flow, and even with the client flow, you need a redirect uri. 
This isn't important because I just want to get both an access and 
refresh token.
Has anyone had any experience with this? Is it  easier to use a more 
developed oauth2 library to handle this? If so, can anyone make any 
suggestions?

If I understand everything correctly, it doesn't matter what library I 
would use to work with the oauth2 protocol, so I could break out of this 
workflow thing that looks like it's more designed for web apps.
Finally, they caution you about being careful about your client id and 
your client secret; is  there much in the way of obviscation or 
something I can do to keep this secret?

-- 
Take care,
Ty
http://tds-solutions.net
The aspen project: a barebones light-weight mud engine:
http://code.google.com/p/aspenmud
He that will not reason is a bigot; he that cannot reason is a fool; he that dares not reason is a slave.

[toc] | [standalone]


Back to top | Article view | comp.lang.python


csiph-web