No, you should act as Identity Provider. Google is the Service Provider. This ensures that your users can use their password to access all of their network, web, and Google resources, as opposed to just Google resources. If you use Google as your IdP, your users can only use that ID for Google resources, and SAML will not work.
On Dec 13, 2007 8:55 PM, g.apps <[EMAIL PROTECTED]> wrote: > > How do we keep the authenication with Google? Google should act as > service provider and identity provider. > > Thanks > > On Dec 13, 7:06 pm, "Ryan Shelley" <[EMAIL PROTECTED]> wrote: > > Check out Google's SAML solution for SSO: > > > > http://code.google.com/apis/apps/sso/saml_reference_implementation.html > > > > On Dec 13, 2007 3:23 PM, g.apps <[EMAIL PROTECTED]> wrote: > > > > > > > > > > > > > We are using the API to successfully create accounts using the API. > > > Now we want to create a custom login where the user would enter their > > > email address & password on our site and we would post it to the > > > Google login page. This doesn't seem to be supported by Google since > > > we are prompted to login again. > > > > > Can this be done with SSO? We don't want to do any authentications on > > > our end. > > > > > Thanks- Hide quoted text - > > > > - Show quoted text - > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
