Google wave user authentication call

[alon]

Hey,
I've been developing a google app engine application for some time. it
currently uses google accounts for registration to my web app.
Everything works great, user is authenticated but when ever he sees a
google wave embed he needs to relogin to google wave.

* Is there any option to make the google wave embed verify his
credentials when he logs to my web app?

* Does google friend connect support google wave for that matter?

[Sheldon Cooper]

Hi alon! This is known issue:

http://code.google.com/p/google-wave-resources/issues/detail?id=840

[alon]

yeah but it referes to google apps account. i just want regular gmail
accounts to be able to authenticate with wave thru my web app.
If i authenticate my user using google accounts login he is logged in
with a session to google. but the embed wave doesnt recognize he is
logged in asking him to login again.

The only thing that keeps the user logged in is using Friend Connect.
but it poses an issue because i need the users email address so i can
invite him to the wave but i dont have it using friendconnect, only
using google accounts.

[pamela (Google employee)]

Okay, so to clarify:
The user has not logged in to their Google account via a normal Google
service (gmail, wave.google.com, etc).
The user logs in to your App via the App Engine users API.
The user is shown as Anonymous on the embedded wave.

If so, I think this is expected. I don't know that we can use the App
Engine authentication to log them into Google Wave.
Are they shown as logged in to other embedded services, like google
docs or spreadsheets?

- pamela

[alon]

hey pamela, thanks for answering.
To clarify, the user logs in using an authenticated call to the Google
Accounts and is forwarded to google.com to authenticate the access of
my webapp to his user details. He is callbacked back to my web app as
authorized.

This is a full authentication with google and he has a session with
any other services.
Why is this method any different then the FriendConnect?

im using Django http://code.google.com/p/app-engine-patch/wiki/GoogleAccounts
to authenticate the user.

Is there any other way? i dont mind using friendconnect, but i need a
users email address inorder to add him as a participant to a wave
automatically and i can get his email only using Google Accounts login
and not friend connect.

Does this clear things abit ? :) appreciate the help. im stuck.


On Jul 11, 4:36 pm, "pamela (Google employee)" <pamela....@gmail.com>
wrote:

[alon]

Just to push this forward.
I want to raise a discussion.

My webapp needs to create new waves with populated content from a
datastore. its a django app on app engine.

Initially i created robot that creates waves and syncs the data with
the datastore. this works fine. well kinda.

Im just wondering. after seeing micro-wave.appspot.com which lets you
create waves using the logged user, should i just try to implement
that so the users on my platform create waves or keep the robot wave
interaction?

On Jul 11, 5:01 pm, alon <alon.car...@gmail.com> wrote:
> hey pamela, thanks for answering.
> To clarify, the user logs in using an authenticated call to the Google
> Accounts and is forwarded to google.com to authenticate the access of
> my webapp to his user details. He is callbacked back to my web app as
> authorized.
>
> This is a full authentication with google and he has a session with
> any other services.
> Why is this method any different then the FriendConnect?
>

> im using Djangohttp://code.google.com/p/app-engine-patch/wiki/GoogleAccounts

[pamela (Google employee)]

We looked into it, and it looks like we cannot use the App Engine user
cookie authentication information to log users into embedded Google
Waves - they need to log in to the wave/gmail account separately.

I would suggest using a robot if you need a robot to do additional
monitoring or manipulating after the initial creation. If you only
need to do the creation, then you could have users authenticate to
your app and create the waves using the data API.

[alon]

i dont want users to re authenticate for the gadget itself. and i
already implemented a whole signup google account procedure, adding
data api to the mix will make authentication a problem.

How can i authenticate a user to my gae webapp by using the wave
scope? is it even possible?

On Jul 20, 3:04 pm, "pamela (Google employee)" <pamela....@gmail.com>

[pamela (Google Employee)]

I've double-checked with both App Engine and Wave teams and confirmed that It's not possible to authenticate the user to the embed API just through your application - they will need to sign in to Google services separately. 

The authentication for your app is only for your app, and we can't re-use that authentication for the embedded wave.

If your application doesn't require real-time editing in the waves, then you could write a simple static renderer of the waves in Django. I'm guessing that it does, however, which means your users will need to login separately.

--
You received this message because you are subscribed to the Google Groups "Google Wave API" group.
To post to this group, send email to google-...@googlegroups.com.
To unsubscribe from this group, send email to google-wave-a...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-wave-api?hl=en.

[alon]

it used to work with google friend connect but stopped all of a sudden
for some reason.

i want to use the embed js because its easier for me to develop a real-
time editing.
the users intention is to edit in real-time together.

its a real shame i cant do anything about it.

did i mention im a Trusted Tester? :) anything?

On Jul 27, 7:22 am, "pamela (Google Employee)" <pamela...@gmail.com>
wrote:

> > google-wave-a...@googlegroups.com<google-wave-api%2Bunsubscribe@ googlegroups.com>
> > .