Wednesday, February 16, 2011

GOC Service Update - Tuesday, February 22th at 14:00 UTC

The GOC will upgrade the following services beginning at Tuesday, February 22th, 2010 at 14:00 UTC. The GOC reserves eight hours (14:00 - 22:00 UTC) in the unlikely event that unexpected problems are encountered. We encourage users to test affected services before the production release.
OIM 2.31 (

ITB version is now available for testing at

(patched) Fixed a bug that prevents resource registration ticket to be created if support center for the resource can not be found (soap element count for assignee field issue)
Improved the way error log was generated during footprint ticket generation.

GOC Ticket 1.33 (

ITB version is now available for testing at

Updated ticket title style for simple ticket updater.
Added a prompt to ask user if user really wants to submit a form without entering any update text.
Changed wording on VO form
(patched) Combined first and last name fields on ticket viewer / editor to be consistent with how name field is handled internally.
(patched) Fixed a bug on custom form (for admin only) error messages
TWiki (

ITB version is now available for testing at; we encourage users to .test this service before the production release.

TWiki's X509 authentication plugin has been replaced by GOC's custom made User authentication module which uses Apache's native x509 feature, and direct access to OIM authe/autho tables. This update will fix FNAL Certificate issue and other issues that have been discovered recently.
Fixed the MIME issue with various MS. Office documents on IE.
Setup forwarding from http to https (like it used to)

MyOSG 1.31 (

ITB version is now available for testing at

Added a link to user feedback form.
Made OpenTickets model more error resistant (in case of GOC Ticket connectivity issue)
(patched) Added missing CSS images

OSG Display (

Modified SQL queries used for Gratia DB which might be causing performance issue (this update has not be finalized yet, and it is experimental until proven effective)

Operating System updates
RHEL operating system patches will be applied to bring systems up to date. A reboot will be required resulting in brief outages during the maintenance period.