News & Blog Posts
2017 Accomplishments Report Documents Community Trust and Identity Efforts
The Internet2 and InCommon trust and identity community reached some key goals during 2017, thanks to the work of dozens of community members participating in working groups, governance and advisory committees, and software and service development.
The Importance of InCommon Federation Baseline Expectations for R&E
Just what value does the InCommon Federation bring to the R&E community anyway? Steve Fleagle, CIO, University of Iowa, spotlights how InCommon maximizes teamwork and minimizes individual organizational effort to achieve secure, painless collaboration through the trust fabric of its members.
Certificate Service Survey Update
Last month's InCommon Certificate Service online survey garnered a 30% response rate, and the feedback—a critical component of service improvement—will be used to develop service work plans for the coming year. Though detailed results are still being drafted, this article provides a few quick takeaways.
InCommon Metadata Health Checks: What’s Up with That?
The good news? Within two weeks of the February 19th "health check" email we have seen a marked improvement in the quality of InCommon Federation metadata. The bad? We still have a very long way to go, with barely over 2% of IdPs and just under 10% of SPs meeting the baseline requirements. Take a look at a before-after snapshot, and find out why the health of your organization's metadata really matters.
R&S Category Key to Supporting Seamless Research Service Access
The Research and Scholarship (R&S) category is crucial to one of InCommon’s main missions: to enable seamless research and academic collaboration. By supporting R&S, Identity Providers share key information with every Service Provider (SP) in the category, providing seamless access to a variety of shared tools, content and services for faculty, staff, and researchers collaborating both nationally and internationally.
Campus Success Program Provides Guidance for TIER Adoption
Want the latest advice from the campus participants and subject-matter experts of the 10-campus-wide TIER Campus Success Program? Check out this summary of working group developments, topic discussions, and blog posts spotlighting real campus experiences—all focused on making your adoption of TIER IAM suite software components more straightforward and successful.
Baseline Expectations: Participation Agreement Changes
The InCommon Steering Committee has approved changes to the InCommon Participation Agreement and the InCommon Federation Policies and Practices (FOPP). The changes are part of the adoption of Baseline Expectations for Trust in Federation, which includes a new dispute resolution process, eliminates the requirement for organizations to post a Participant Operational Practices (POP) document in favor of requiring certain elements to be present in the InCommon trust registry (also known as “metadata”).
In keeping with the InCommon charter and bylaws, the revised Participation Agreement goes into effect on June 15, 2018, 90 days after notice was sent on March 15. Changes to the FOPP are effective as of the Steering Committee action on March 4.
The InCommon community’s work on Baseline Expectations now enters a transition phase as we collectively gear up to support this new program. Look for more on the new dispute resolution and consensus process development/refinement in the coming weeks.
Information about the Baseline Expectations program is available on the InCommon website. There is also a Baseline Expectations wiki space, which includes links to informational webinars, an implementation roadmap, and an FAQ.
Key Internet2 identity initiatives are supported in part by National Science Foundation grants. For more information, see specific software sites.
Visit the Internet2 Email Preferences Center to manage your email subscriptions for the Trust and Identity Newsletter, and consider subscribing to the Community Update or other newsletters of interest.