UCTrust Workgroup
Child pages
  • eAcademyUpdate

Versions Compared

Old Version 10

changes.mady.by.user Wu, Albert

Saved on

compared with

New Version 11

changes.mady.by.user Wu, Albert

Saved on

Key

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

...

eAcademy is already a member of InCommon. It has also completed similar integration with member schools in several federations.

Status

August 12, 2010

The UC Trust subgroup met with eAcademy via conference call to discuss options for asserting individual's eligibility to download MS software under MCCA. Two options were discussed. eAcademy can support either.

 

Option 1 - Shibboleth Attribute Assertion

Option 2 - Back Channel Data Feed

Description

Campus IDP aggregates local MCCA eligibility data and transforms it into eduPersonEntitlement values.

Campus prepares back channel data feed, either via IDM office or Software Licensing office and delivers to eAcademy. eAcademy resolves individual's eligibility using supplied feed and user identifier (most likely ePPN) coming through Shibboleth.

Pro

  • There is no separate data feed out of the campus. One less process to maintain.
  • The technique better aligns with Shibboleth practice and scales better in the long run.
  • Back channel feed may be easier to implement for the IDP, especially if the Software License office already tracks individual eligibility in a central database.

Con

  • Depending on the IDP's readiness to assert entitlement values, this can trigger substantial work on the IDP side.
  • The technique is another one off data feed. It doesn't scale well longer term.

History

August 12, 2010

...

There were a few additional details:

  • Under UC's MCCA license terms, departments can selectively license individual software products. That means the campus will need to somehow express not only who is eligible, but also which software the individual is eligible for.
  • Even though we want to have a consistent data provisioning mechanism from the UC Trust perspective, eAcademy can and is willing to support different integration options by campus.
  • So far, UCLA and UCI are definitely going forward. UCD most likely will do so. UCSC is following with keen interest.

Action Items:

  • Albert will write up a proposed design spec for Option 1.
  • We need volunteer to write up in greater detail how the back channel feed will work. In particular, we need to define data format and transmission mechanism.
  • UC Trust to discuss at the Aug. meeting (update: the Aug. UC Trust meeting was canceled. We'd most likely move this to the UC Trust discussion list)

History

June 2010

Tom Trappler reports that based on his conversation with Microsoft, the campuses do need to assert individuals' eligibility. The individual cannot self-identify.

...