This document details the changes from ISIS 4 to ISIS 5.

General

  • Bruin Online Logon ID has been renamed to UCLA Logon ID.
  • UID/PIN authentication has been removed. Users who previously used UID/PIN to login will now be prompted to use their UCLA Logon ID to login. Links have been set up to take a user to CTS to create a new UCLA Logon ID if he/she does not have one.
  • UCLA Logon ID will now always be the first login type listed.
  • ISIS no longer raises the 604010 error when the user IP address changes in between calls to ISIS. Instead, these conflicts will be monitored in internal security logs.
  • ISIS now uses the Enterprise Directory as its source for user data.

User Interface

  • A UCLA Visual Identity compliant UI is now in place.
  • The new UI uses XHTML and cascading stylesheets. Applications can now submit custom cascading stylesheets to customize the look and feel of their login pages.
  • The Directory of ISIS Applications page has been temporarily disabled.
  • A “logout” page is now available. Instead of calling the logout web service, an application can optionally redirect the user to the logout page to log a user out of ISIS.
  • If provided, the helpdesk contact information for the application will be displayed on the login page by default.

Data

  • All user attributes returned in the ISIS VerifySession call are now essentially returned twice in the same call, once with their legacy parameter names, and once with their new standard URN parameter names. This change is to provide a migration path to user standardized data attribute names across all EDIMI services. We recommend applications to beging adopting the new URN names.
  • There is no longer a 24 hour delay in the binding of UID and UCLA Logon ID (formerly BOL ID). This binding now occurs in real time in the Enterprise Directory (hence ISIS) as each logon ID is created.
  • Email address updates from URSA now show up in real time in the Enterprise Directory.
  • There is a now a separate test UCLA Logon ID engine. Login attempts going through test ISIS will go against the test UCLA Logon ID engine.

Programming Interface

There is no programming interface change from ISIS 4 to ISIS 5.

Administration

  • Application profiles can no longer be shared between test and production ISIS. The ISIS team will help each application set up appropriate test and production profiles.
  • Starting with ISIS 5, we require 3 sets of contact informaiton when registering an application:
  • The Administrative Contact is the person who has the overall management responsibility for the application.
  • The Technical Contact is the person who has the day to day technical (programming and/or system administration) responsibilities.
  • The Help Desk is the entity who provides the end user support for the application. We will collect these information at each application’s set up time.