...
The 6 months for compliance applies to InCommon but not to IdPs.
We don't know what this means for our IDPsStarting . We are starting discussions to see what is the impact to the InCommon Assurance program and the community. The question came up about what are the service providers they are working with first? The Veterans Admin is the biggest one.
Most campuses don't want their faculty and staff leverage their campus credentials to interact w consumer based services like the VA
They want to use their credentials for grant submissions and teaching resources or dept of Ed resources.
So we are trying to find out from FICAM, what is the ETA for the services that are more related to higher ed?
The answers to these questions will help the AAC determine how to support FICAM 2.0
There is interest in exploring assurance for research
and in developing developing a community profile to address research needs.
There has been been a request for a community profile that is more multi factor oriented
The hope is to address the needs of the SP s those SPs that are of interest to the InCommon community And and the needs of the IDP s IDPs for good practices The . The AAC is is trying to come up with a happy medium medium that grows the trust level of the InCommon federation in a logical way.
Scott Koranda: have you had input from Steering or TAC on the amount of effort to continue to put into FICAM?
Ann: no input directly from Steering on this. InCommon TAC wants to make assurance relevant to the community as a whole
...
Multi Context Broker code is ready, see:
https://wiki.shibboleth.net/confluence/display/SHIB2/Multi-Context+Broker
David is putting together some documentation
...