Last minute update: We're experiencing trouble with audio today.
You will need to dial-in to hear the audio; it will not be available
via Adobe Connect.
David
On 03/15/2014 12:06 PM, David Walker
wrote:
I neglected to include dial-in information for those who would
like to participate in Wednesday's discussion. My apologies. You
will be able to listen via Adboe Connect, and there will be a chat
session, but to speak you will need to use the phone. Here are
the complete connection instructions:
Date and time: Wednesday, March 19, 2014, 2:00-3:00
EDT
Adobe Connect: http://internet2.adobeconnect.com/mfa-cohortium
Dial-in numbers:
+1-734-615-7474 (English I2, Please use if you do not pay for
Long Distance),
+1-866-411-0013 (English I2, toll free US/Canada Only)
PIN: 0106400#
(Please mute your Adobe Connect speakers if you use the
phone.)
David
On 03/14/2014 01:09 PM, David Walker
wrote:
InCommon Assurance Implementers
MFA Cohortium
David Langenberg of the University of Chicago will be presenting
and demonstrating the Multi-Context Broker in a joint meeting of
the MFA Cohortium and the InCommon Assurance Implementers next
Wednesday:
Date and time: Wednesday, March 19, 2014, 2:00-3:00
EDT
Adobe Connect: http://internet2.adobeconnect.com/mfa-cohortium
All are welcome; please join us. If time permits, there will be
an abbreviated Cohortium meeting following the presentation.
David Walker
Mike Grady
Ann West
The Multi-Context Broker
Is your campus considering the implementation of multi-factor
authentication to bolster security beyond passwords? If so, and
you use Shibboleth single sign-on software, your job just got
easier.
The Internet2 community is releasing an extension to the
Shibboleth software that makes it easier for your organization
to support the increasing demand for multi-factor authentication
and simplify the user experience. This extension, the
Multi-Context Broker (MCB), significantly eases the integration
of multi-factor authentication technologies and the management
of InCommon Assurance Profiles.
Now with the MCB, organizations can easily support single
sign-on for multiple authentication methods. No custom code is
needed. Once configured, MCB automatically selects appropriate
authentication methods, based on service provider requests, user
certifications, user choice, and hierarchies of assurance
profiles like InCommon Bronze and Silver. The MCB currently
supports username/password, X.509 client certificates, and Duo
Security as authentication methods, and more methods are in the
works.
Further information about the Multi-Context Broker is available
from the InCommon Assurance wiki space: https://spaces.internet2.edu/x/BozFAg
|
