Authentication without having a browser
Bascy
Alexander Skwar
You don't have to do the auth on the same system. And IIRC, you
could also use text browsers like lynx, w3m, ... to do the auth.
Alexander
--
↯ Lifestream (Twitter, Blog, …) ↣ http://alexs77.soup.io/ ↯
↯ Chat (Jabber/Google Talk) ↣ a.s...@gmail.com , AIM: alexws77 ↯
Bascy
Alexander Skwar
On Fri, Mar 11, 2011 at 14:58, Bascy <b...@basbex.com> wrote:
> So if i authorize on a different system, how do i tell googlecl abou this?
> Do i set some config option? transfer a autorisation-file?
Uhm, aren't the instructions printed clear enough? ;)
--($ ~/Src)-- google docs list
Please specify user: a.×××
Please log in and/or grant access at
https://www.google.com/accounts/OAuthAuthorizeToken?oauth_token=4×××&hd=default
Please enter the verification code on the success page:
That's how. Did you not get this?
Bascy
Tom Miller
That's not a good response. Could you file a report on the issue tracker?
In the meantime, try setting the auth_browser setting in the configuration file to None. I think that will bypass the check for a browser.
- Tom
Alexander Skwar
Interesting ;)
Well, why don't you install a browser? Comes handy quite
often, I think *G* Doesn't need to be graphical, so w3m,
links or lynx are good enough.
Oh, and of course try what Tom suggested *G*
Bascy
Alexander Skwar
On Fri, Mar 11, 2011 at 15:36, Bascy <b...@basbex.com> wrote:
> Its a NAS, so its main task is storing files, and running some processes
> dedicated to those files. 99.9% of the time this thing runs on its own, with
> no user involvement.
Well, so? Even on a NAS *I* find it useful to be able to view
stored HTML files, for example. I mean, really, it's not like
w3m/lynx/links are huge - after all, we're talking about a
NAS, so size of programs shouldn't be a matter anyway *G*
> So i don't want to install a browser.
Okay. I don't have to understand everything, do I? *G*
> Besides, what's the use of a commandline tool if it can't be run on its own
> because it still requires a browser...
It doesn't. Just for the auth and even the auth can be done somewhere
else.
> Anyway, i understand from Tom Millers respons that it isnt supposed to work
> the way it does now on my server.
You can of course run google cl on your server. It needs a
"BROWSER", though. If you really don't want to install
a browser (?), then I think the easiest way would be to tell
googlecl (or python, really) to use echo instead. Python
can be told what browser to use by setting the BROWSER
environment variable. Maybe like so:
--($ ~)-- env BROWSER=/bin/echo google docs list
Please specify user:×…
https://www.google.com/accounts/OAuthAuthorizeToken?oauth_token=4×…&hd=default
Please log in and/or grant access at
Please enter the verification code on the success page:
(That's from Linux. Dunno where your system has an executable
standalone echo)
Regards,
Bascy
Alexander Skwar
On Fri, Mar 11, 2011 at 15:26, Tom Miller <tom.h....@gmail.com> wrote:
> In the meantime, try setting the auth_browser setting in the configuration
> file to None. I think that will bypass the check for a browser.
That's going to be problematic to do, if he doesn't yet have a
configuration file *G* Of course, he could write one in the
correct syntax manually, but… :)
Gonna repeat what I just wrote — the easiest way in such a
case is to fool googlecl or Python into using something like
"echo" as a browser, eg. like so:
--($ ~)-- env BROWSER=/bin/echo google docs list
Please specify user: ×××
https://www.google.com/accounts/OAuthAuthorizeToken?oauth_token=4×&hd=default
Please log in and/or grant access at
https://www.google.com/accounts/OAuthAuthorizeToken?oauth_token=4×&hd=default
Please enter the verification code on the success page:
And then the user is to go to this google…/…OAuth… URL.
Tom Miller
> Hi!
>
> On Fri, Mar 11, 2011 at 15:26, Tom Miller <tom.h....@gmail.com> wrote:
>
>> In the meantime, try setting the auth_browser setting in the configuration
>> file to None. I think that will bypass the check for a browser.
>
> That's going to be problematic to do, if he doesn't yet have a
> configuration file *G* Of course, he could write one in the
> correct syntax manually, but… :)
One of the first things GoogleCL does is generate a config file, so
there (thankfully) won't be a need to do that. And at some stage of
the authentication process, a browser is necessary, though it can be
on a completely different machine. You'll just have to copy the token
file to the appropriate directory. Token files typically reside in
~/.local/share/googlecl
>
> Gonna repeat what I just wrote — the easiest way in such a
> case is to fool googlecl or Python into using something like
> "echo" as a browser, eg. like so:
>
> --($ ~)-- env BROWSER=/bin/echo google docs list
> Please specify user: ×××
> https://www.google.com/accounts/OAuthAuthorizeToken?oauth_token=4×&hd=default
> Please log in and/or grant access at
> https://www.google.com/accounts/OAuthAuthorizeToken?oauth_token=4×&hd=default
>
> Please enter the verification code on the success page:
The URL should be printed automatically, whether or not the browser is
launched. So getting this issue resolved should solve the problem as
well.
- Tom