Pragmatic workaround to "less secure" authorization restrictions?

I am the developer of MarsEdit, a popular Mac blogging app that includes 
support for Blogger.

Because MarsEdit has been around for a long time, it happens to still use 
The Blogger v2 GData API, and uses ClientLogin for authorization. I 
understand that moving to both the v3 API and to OAuth 2.0 for 
authorization is advised.

In the mean time, however, I am facing the problem that users are having 
requests from MarsEdit rejected because of the use of "less secure" 
authorization method. In order to continue using MarsEdit, they need to 
turn on support for "less secure" mode in their Google settings. I can 
easily understand how this is off-putting to most users.

So, I'd like to adopt a "more secure" authorization method ASAP, ideally 
before taking the time to move to the v3 API.

It appears that I can use the OAuth 2.0 (or 1.0 for that matter) API in 
conjunction with the v2 API, so that might be the way forward.

Is there any way to use Google's OAuth 2.0 or 1.0 authorization API to log 
a user in without the explicit "user consent" phase? Something akin to 
Twitter and Tumblr's "xAuth" which allows a one-time exchange of username 
and password for a persistent token? I suspect the answer is no, but I 
thought I would ask so I can adopt the most pragmatic solution ASAP. The 
longer solution of adding full support for OAuth 2.0 (with GUI user 
consent) will obviously take longer.

Thanks for your help and advise!

Daniel

-- 
You received this message because you are subscribed to the Google Groups "Blogger Developer Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/bloggerdev.
For more options, visit https://groups.google.com/d/optout.