Commit graph

7 commits

Author SHA1 Message Date
Martin Wilke
bb86cbe5d2 - Get Rid MD5 support 2011-03-20 12:54:45 +00:00
Philip M. Gollucci
6564a2589c - only 13% of the p5- ports embed @comment $FreeBSD$:
so standarize and remove it

With Hat:   perl@
2010-09-24 02:03:44 +00:00
Andrej Zverev
f4847a9399 Update to 0.10.
PR:		ports/149463
Submitted by:	Frederic Culot <frederic@culot.org>
2010-08-18 11:09:20 +00:00
Yen-Ming Lee
06b8111394 - update to 0.09 2009-11-09 09:43:37 +00:00
Martin Wilke
c5b9f4b3fa - Update to 0.08
- Pass maintainership to perl@

PR:		138044
Submitted by:	Gea-Suan Lin <gslin@gslin.org> (maintainer)
2009-08-22 19:22:07 +00:00
Steven Kreuzer
396889f975 Add missing dependencies
PR:		ports/137475
Submitted by:	Gea-Suan Lin <gslin@gslin.org>
2009-08-07 18:34:04 +00:00
Martin Wilke
46dc595cbb Google::SAML::Response can be used to generate a signed XML document
that is needed for logging your users into Google using SSO.

You have some sort of web application that can identify and
authenticate users. You want users to be able to use some sort of
Google service such as Google mail.

When using SSO with your Google partner account, your users will send
a request to a Google URL. If the user isn't already logged in to
Google, Google will redirect him to a URL that you can define. Behind
this URL, you need to have a script that authenticates users in your
original framework and generates a SAML response for Google that you
send back to the user whose browser will then submit it back to
Google. If everything works, users will then be logged into their
Google account and they don't even have to know their usernames or
passwords.

WWW:	http://search.cpan.org/dist/Google-SAML-Response/

PR:		ports/137445
Submitted by:	Gea-Suan Lin <gslin at gslin.org>
2009-08-05 12:24:31 +00:00