...
- AYSO
- Bruce James presented a few slides showing AYSO use via UCTrust to date.
- UCD, UCI, UCR, and UCSD are enabled for UCTrust access to AYSO. UCI and UCSD have rolled it out to their communities.
- The usage statistics show that there is no strong preference among AYSO users regarding the option to continue to prompt for the AYSO password at the start of a session. It appears that giving users the choice was the right thing to do. It did create some minor confusion at UCI about the difference between the AYSO password and the UCInetID password.
- Connexxus
- David Walker discussed the two documents that were distributed with the agenda, SystemIssues-2008-03-20.doc and Re: Trondent Standard Profile fields.
- Connexxus's UCTrust interface will use eduPersonPrincipleName to identify the user and will require UCTrust Basic assurance.
- There will be two versions of the profile feeds. Version 1 will address the first two locations' needs (UCR and UCSD), and Version 2 will address all locations' needs. Version 1 should be final very soon.
- HR LMS (aka UC Learning Center)
- The UC Learning Center's UCTrust interface is in production and is starting to see use from the campuses.
- Recent InCommon Level of Assurance discussions
- The registration requirements for UCTrust, InCommon Silver, and eAuthentication level 2 are still difficult for campuses, particularly for remote users.
- There is at least one service that can call a telephone and "speak" some information. Such a service could be used to "...confirm existing records of the registrant's electronic mail address, telephone number, or postal address," as described in UCTrust's remote registration requirements.
- Notary Publics were also suggested to support remote registration processes.
- The registration requirements for UCTrust, InCommon Silver, and eAuthentication level 2 are still difficult for campuses, particularly for remote users.
...