More info?

Thanks for your interest. I think you may misunderstand the purpose of the module (though feel free to correct me). This module is a part of the Google Apps single sign on API (http://code.google.com/apis/apps/sso/saml_reference_implementation.html). Thus, I cannot provide examples easily (though I am creating some screenshots of the Google Apps admin interface where you set it up.)

There is still room to provide clarity on the capabilities/limitations.

When I first saw this, I thought "hey, this is a way to get around paying for LDAP->Gapps support... I can just route Gapps through Drupal, and use the ldap_integration module to..." and then I realized that I have no idea how* this module interacts with the UserDB...

So, can it passthrough other authentication modules, or does this ONLY work for sites using the built-in user auth system? More to the point, is there any way to support both*?

Thanks!

-deano

Thanks for pointing out the ambiguity in my description. The prerequisites for this module are the following:

1) A google apps account that supports the SSO API access (i.e. Education or Enterprise)
2) The $user->name must be correctly populated with the username you want the module to send to google (typically automatic)
3) xmlsec (www.aleksey.com/xmlsec/) must be installed on the server
4) You must have generated a private/public keypair (for instructions, see Google's docs on the subject)

Note that this module does let you limit SSO authentication services to particular group(s) of users.

I'll be adding docs to effect shortly.