Access to Multiple Systems

For the term starting Jan 7, we have students who need to be directed to the new Vista system (v8). By standard practice, students also have access to the previous term a few weeks into the new term, let’s say Feb 23. So we’ll need to ensure some access to the old Vista system (v3).

There are multiple ways we can handle this access:

  1. School VIPs – We highly encourage users bookmark, publish links, and access school VIPs instead of the actual address. The idea being these addresses will always go to the right place. Other addresses could change and not work. We even have a v8 version for pre-cutover access and a v3 version for post-cutover access. The problem seems to be some campuses and users continue to use the addesses other than the school VIPs (v8 will only show them the school VIP).
  2. Custom login page – We would place an HTML file on the v3 system explaining general access has moved. Some people would need to get past this page and into the v3 system. The questions here are:
    1. Can we just give the admins the link to bypass the custom login page? They could then manage who has access to the site. They might have to provide this “secret” to thousands of students.
    2. Do we dare publish the link on the page? Something like “To check Fall 2008 grades: click here.”
  3. Deny access – We would deny access to all users except those who hold the Institution Administrator role in v3. The holders of that role would then be responsible to granting access one-by-one to other users who need to access to this old system.
  4. f5 iRule to 302 Redirect – We do host a school who uses autosignon. It is conceivable we could intercept attempts to login and redirect them to the correct host. It would be much better for them just to use the School VIPs solution.

Anyone have a better solution?