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.
Remove WWW entries moved into port Makefiles
Commit b7f05445c00f has added WWW entries to port Makefiles based on
WWW: lines in pkg-descr files.
This commit removes the WWW: lines of moved-over URLs from these
pkg-descr files.
Approved by: portmgr (tcberner)
Add WWW entries to port Makefiles
It has been common practice to have one or more URLs at the end of the
ports' pkg-descr files, one per line and prefixed with "WWW:". These
URLs should point at a project website or other relevant resources.
Access to these URLs required processing of the pkg-descr files, and
they have often become stale over time. If more than one such URL was
present in a pkg-descr file, only the first one was tarnsfered into
the port INDEX, but for many ports only the last line did contain the
port specific URL to further information.
There have been several proposals to make a project URL available as
a macro in the ports' Makefiles, over time.
(Only the first 15 lines of the commit message are shown above )
net: remove 'Created by' lines
A big Thank You to the original contributors of these ports:
* <ports@c0decafe.net>
* Aaron Dalton <aaron@FreeBSD.org>
* Aaron Straup Cope <ascope@cpan.org>
* Aaron Zauner <az_mail@gmx.at>
* Adam Jette <jettea46@yahoo.com>
* Adam Weinberger <adamw@FreeBSD.org>
* Alan Eldridge <alane@geeksrus.net>
* Alex Bakhtin <Alex.Bakhtin@gmail.com>
* Alex Deiter <Alex.Deiter@Gmail.COM>
* Alex Dupre <ale@FreeBSD.org>
* Alex Dupre <sysadmin@alexdupre.com>
(Only the first 15 lines of the commit message are shown above )
Fix every instance of RUN_DEPENDS:=${BUILD_DEPENDS} in p5 ports, except
for where it resulted in a change in output from build-depends-list or
run-depends-list.
Approved by: portmgr (adamw)
Change the way Perl modules are installed, update the default Perl to 5.18.
Before, we had:
site_perl : lib/perl5/site_perl/5.18
site_perl/perl_arch : lib/perl5/site_perl/5.18/mach
perl_man3 : lib/perl5/5.18/man/man3
Now we have:
site_perl : lib/perl5/site_perl
site_arch : lib/perl5/site_perl/mach/5.18
perl_man3 : lib/perl5/site_perl/man/man3
Modules without any .so will be installed at the same place regardless of the
(Only the first 15 lines of the commit message are shown above )
Remove backslashes from single- and double-quotes in COMMENT and _DESC
strings, that were passed through rather than escaping anything.
Approved by: portmgr (not really, but it touches unstaged ports)
- Revert ports/165605 as requested by portmgr@
Note: devel/p5-B-Size and devel/p5-Devel-Arena
where intentionally not restored.
PR: ports/165605
Approved by: portmgr (bapt)
Feature safe: yes (I sure hope so)
- Remove ports that only work with < perl 5.12 (devel/p5-B-Size,
devel/p5-Devel-Arena)
- Remove conditionals for PERL_LEVEL < 501200
- Remove regression-test targets b/c this will be centralized in Mk/bsd.perl.mk
- Other minor cleanups
RUN_DEPENDS = ${BUILD_DEPENDS} -> RUN_DEPENDS:= ${BUILD_DEPENDS}
PR: ports/165605
Submitted by: pgollucci (myself)
Approved by: portmgr (linimon)
Exp Run by: linimon
Tested by: make index
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>
