Deprecated
Note that this page has been deprecated; the information it contains is no longer current. It has been retained for historical purposes only.
On 2 February 2011, a redirect from the InCommon WAYF to the Discovery Service was put in place and the WAYF was scheduled for complete removal on 6 July 2011. In the interim, service providers throughout the Federation were advised to adjust their software configurations to point at the Discovery Service, not the WAYF.
As of 28 July 2011, the InCommon WAYF is still receiving a relatively small number of requests. For instance, during the week from July 21 to July 27, the legacy WAYF received the indicated number of requests from users trying to access the following InCommon service providers:
1 https://ersqa.ucop.edu 51 https://expo.uw.edu/shibboleth 12 https://express.travel.ucla.edu/shibboleth/incommon 4 https://grid.ucr.edu/shibboleth 1 https://internet2.edu%25Fshibboleth 4 https://pcardstage.finance.ucla.edu/shibboleth/incommon/sp 1 https://shib-db.grnoc.iu.edu/shibboleth 36 https://shib.lynda.com/shibboleth-sp 1 https://spaces.ais.ucla.edu/incommon 1 https://staff.internet2.edu/shibboleth 3 https://uc.sumtotalsystems.com/shibboleth 1 https://uca.sumtotalsystems.com/sh 2 https://uca.sumtotalsystems.com/shibboleth 21 https://ucsso.travelprefs.com
The URLs listed above are actually the entity IDs of each service provider. It's possible that these SPs are still redirecting users to the legacy WAYF (which is a software configuration issue), but it's much more likely that users are selecting bookmarks or clicking on links that mistakenly point to the legacy WAYF. This is indicated in the InCCollaborate:attached log file entries for these requests, some of which show an HTTP Referrer, which suggests the user may have clicked a link on a web page.