An important question is: what are the service providers FICAM will be working with first? The Veterans Admin is a big one.
InCommon is aware that many campuses don't want their faculty and staff to leverage their campus credentials to interact w consumer based services like the VA.
They want to use their campus credentials for grant submissions and teaching resources or for interactions with the Dept of Ed.
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 our community in exploring/pursuing assurance for research
and in developing a community profile to address research needs.
There has also been a request for a community profile that is more multi factor multifactor oriented. The hope is to address the needs of those SPs that are of interest to the InCommon community and the needs of the IDPs for good practices. The AAC is trying to come up with a happy medium that grows the trust level of the InCommon federation in a logical way.
Scott: has the AAC 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 has been working on priorities and has passed along some 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.
There are opportunities in the community that are more compelling for the TAC than FICAM.
Scott: As there are If new profiles are developed for HE or for Resrearch
Will and Research will there be a chance to help influence Federated Incident Response ? That is in the profiles from the beginning?
Ann: The first step is requirements gathering and LIGO will have a . Eventually yes, there will be the chance to provide input