Page History

...

When the UCTrust Wireless project started, eduroam-US was not widely deployed, and our strategy was "... that federating our web portals with Shibboleth is the best first step.  We will track eduRoam progress in the US and plan to federate access to our encrypted networks when it seems appropriate to do so."  We did this, as it seemed the most effect way to make quick progress toward federating UC's wireless guest networks.

While there are some campuses have issues associated with adopting eduroam-US as it is today, we now propose that our first step toward that goal be to join eduroam-US, start using its services, and work within it that federation to resolve the issues. The originally-planned federated captive portal will could be the strategy for situations where 802.1x is not a feasible technically, or where the operational impacts of eduroam-US are too great. The However, a bifurcated strategy will increase user frustration and will not provide seamless roaming between UC campuses. In addition, the captive portals are likely to take longer to implement, however, as eduroam-US is a relatively fast implementation for many campuses.

...

• Host institutions require information about their guests.  This information is used to communicate with guests in the following situations:
  • A security vulnerability is suspected on a guest's computer.
  • A copyright infringement notice is received for a guest.
  • A security investigation involves a guest.
• Host institutions need may desire to present local information, such as its network policy, to guests.
• A wireless guess access federation needs policies to govern operational issues and other interactions among its members.

...