Hi Alex I've rated this post as 5 stars as it's explained something quite succinctly that isn't explained anywhere else on the google documentation. I'm certain all of the words and facts are in the documentation but they're so spread out that I've found it hard to piece together.
I'm disappointed that there is no SSO solution that 3rd party web applications can use easily, but thems there the breaks and now we have to find a way around this issue. Alex, there must be a way to build a 3rd party web app that can use SSO/AuthSub to log the users into their google hosted apps domain, and then somehow pass authentication for the email, chat and the personal calendar back to google without asking these users to login a further 3 times? There is another post I'm following http://tinyurl.com/69pky7 where douglas is talking about synchronising the passwords in google and the AD, is this one way of achieving the result I'm after? Is there a way to get our local CAS server, the ID provider in my case, to act as a proxy? So instead of switching SSO in google, we go to the CAS server initially for authentication, and then that connects to all the different google API's and authenticates the user and passes the client back all the information it needs to login to the hosted domain and the different google data API's? Any advice would be greatly welcomed, there seems to be a lot of confusion out there about this issue and it would be great if we could clear it all up. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Apps APIs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/google-apps-apis?hl=en -~----------~----~----~----~------~----~------~--~---
