Child pages
  • Minutes of Assurance Call of 12-Feb-2014

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


Ann: InCommon TAC has been working on priorities and has passed along its recommendations to Steering. TAC wants to make assurance relevant to the community as a whole. One approach is to set a baseline set of practices for the community, to bring up the trust level. This can potentially address the fact that the current POP (Participant Operational Practices) document does not provide sufficient transparency to help SPs and IdPs fully understand the identity practices in effect.

Scott:   If new profiles are developed for HE and Research will there be a chance to help influence Federated Incident Response in the profiles from the beginning?

Ann: The first step is requirements gathering. Eventually yes, there will be the chance to provide input

AD Assurance Update

David Walker reported that the comment period for the AD Assurance work closed at the end of January. 

The comments that were received have resulted in some small tweaks to the document. Soon there should be an announcement of publication of the 2014 version of the AD Assurance Cookbook

Multi Context Broker


David reported that the Multi Context Broker (MCB) code is ready, see:

David is putting has put together some documentation Something that introduces concepts and why they may want to be interested  in the MCB

David will link from the top level assurance page / project status page

It is close and we will be sending out an announcement soon

Document introduces concepts , gives some examples of how it might be used

Does not go real deep into installing and configuring

And provides link on where to get the code and config instructions

Will be using the Shib users list The Shib users list will be used for questions and comments Stored on the MCB

The code is stored on GITHUB on internet2 an Internet2 space

There is an issue tracker we will be using for bugs