Blog from March, 2017

Internet2 has started deployment of a new service desk, ServiceNow. As of March 27, all email sent to our support address (admin@incommon.org) will create a ticket in ServiceNow, which will generate an automated email response The same set of InCommon/Internet2 people will respond to requests through the new service desk system. We will continue to use admin@incommon.org for support requests from participants and certificate service subscribers.
 
Over the last three years, we have seen significant increases in the volume of mail to admin@incommon.org. ServiceNow will help us organize and respond to your requests in a more efficient and timely manner. We hope you find this change helpful, and we're always open to your feedback (email admin@incommon.org). Increased maturity in both service delivery and operations are among InCommon’s main work areas for 2017, and this move to ServiceNow is critical to achieving those goals.

March 22 TAC Work Plan Webinar

Wednesday, March 22, 2017
2 pm ET | 1 pm CT | Noon MT | 11 am PT
https://internet2.adobeconnect.com/iam-online

The InCommon Technical Advisory Committee (TAC) will present its draft 2017 work plan during this webinar, March 22, at 2 pm ET. The TAC provides recommendations related to the technical operation and management of InCommon. The work plan outlines the proposed technical priorities, particularly for the InCommon Federation.

This webinar is intended to gather community feedback on the work plan. This year’s draft plan includes these topics (among others):

  • Support for OAuth/OpenID Connect

  • Improving IdP discovery (Discovery 2.0)

  • Less restrictive attribute release policies

  • Improve Service Provider onboarding processes


Please plan to join us to learn about the 2017 plans and provide feedback and suggestions.

The OpenID Connect Survey Working Group, chartered by the InCommon Technical Advisory Committee (TAC), recently conducted a study to understand the community’s interest and use of OIDC/OAuth protocols. The survey also asked how InCommon and Internet2 may help campuses in the adoption of these protocols.

The results are in. The survey working group has compiled a report summarizing the survey findings and the working group's recommendations. You are invited to review the report and provide feedback. The deadline for comments is March 24, 2017.

Shibboleth Installation Workshop - June 13-14, 2017 - Denver, Colorado

InCommon Shibboleth Installation Workshop
June 13-14, 2017
University of Denver
Denver, Colorado

Registration: www.incommon.org/shibtraining

Denver details: https://spaces.at.internet2.edu/x/rIKTBg

Registration is open for the an InCommon Shibboleth Installation Workshop June 13-14, at the University of Denver. The two-day training sessions cover both the Identity Provider and Service Provider software, as well as some integration issues. The workshops focus on installing and deploying IdPv3 and the Shibboleth Service Provider. Here is what you can expect:

    •    A two-day, directed self-paced workshop

    •    Hands-on installation of the identity provider and service provider software

    •    Experienced trainers providing overviews and one-on-one help 

    •    Discussions on configuration and suggested practices for federation

    •    Attendance is limited to 40


The workshops will offer the chance to:
    •    Install a prototype Shibboleth identity or service provider in a virtual machine environment

    •    Discuss how to configure and running the software in production

    •    Learn about integration with other identity management components such as LDAP and selected service providers


Knowledge of identity management concepts and related implementation experience is strongly recommended. Organizations are encouraged to send one or two attendees who best represent the following functions:

    •    System install, integration, and ongoing support staff

    •    Campus technology architects


To learn more about Shibboleth, see the Shibboleth wiki (wiki.shibboleth.net). More information on federated identity can be found at www.incommon.org.