On Thursday, February 9, 2006, AIS will be performing an upgrade to the ISIS system. We do not expect any outages during this upgrade. Users should not experience any service interruption.

Even though we do not expect outages, if your application uses ISIS, Please monitor your application more closely on Thursday afternoon and report suspected ISIS problems to AIS.

Below is a list of changes implemented in this upgrade.

Repair an illegal cookie value used by ISIS Login Server.

The ISIS Login Server checks for a brower’s cookie support by inserting a test cookie to the user’s browser. The previous value used in this cookie was not compliant with the HTTP protocol. It is being repaired in this version.

ISIS now returns additional attributes to applications in the VerifySession Response.

The updated ISIS module now returns up to 3 additional attributes in its VerifySession response. These are middle name, suffix, and BOL returned UID.

Middle Name and Suffix

Users have requested that we return an individual’s middle name and suffix as part of the returned data. It is being implemented in this version. The attributes’ parameter names are “MiddleName” and “SuffixName” respectively. These additional attributes, like other user attributes, are returned in the section of the VerifySession response.

Bruin Online Returned UID

Due to the batch update processing of BOL ID/UID mapping data, there is currently an overnight lag for newly created BOL ID’s to be mapped the owner’s UID in ISIS. While this lag is being addressed in the new Enterprise Directory based ISIS implementation later in the year, we are implementing a workaround for applications requiring immediate access to BOL ID/UID mapping data.

As of this version, we are returning the user’s UID as reported by the BOL authentication interface during a BOL authentication event. As is the case with middle name and suffix, we are returning this data in the section of the VerifySession response.
The name of this data parameter is “BolReturnedUclaID”.

NOTE: This element appears in the verifysession response only if a user logs in with his/her BOL ID.

Example

Joe Bruin logs in using his BOL ID jbruin. Currently, this is what you’d see:

 <userAttributes>
   <attribute name="UID" value="000111222" />
   <attribute name="LastName" value="BRUIN             " />
   <attribute name="FirstName" value="JOE             " />
   <attribute name="Email" value="JBRUIN@UCLA.EDU        " />
   <attribute name="CampMailCode" value="999999" />
   <attribute name="CampPhone" value="3108254321" />
 </userAttributes>

In the new version, you’d see:

 <userAttributes>
   <attribute name="UID" value="000111222" />
   <attribute name="LastName" value="BRUIN" />
   <attribute name="FirstName" value="JOE" />
   <attribute name="MiddleName" value="F" />
   <attribute name="SuffixName" value="JR" />
   <attribute name="Email" value="JBRUIN@UCLA.EDU" />
   <attribute name="CampMailCode" value="999999" />
   <attribute name="CampPhone" value="3108251212" />
   <attribute name="BolReturnedUclaID" value="000111222" />
 </userAttributes>

Please send questions and comments to albertwu@ucla.edu.