Wednesday, April 18, 2012

Tuesday, April 24th at 13:00 UTC

The GOC will upgrade the following services beginning Tuesday, April 24th, 2012 at 13:00 UTC. The GOC reserves 8 hours (13:00 - 21:00 UTC) in the unlikely event that unexpected problems are encountered. We encourage users to test affected services before the production release.
OIM 3.0

ITB version is now available for testing at

*Enabling http access for guest user access. Redefined user types and redesigned the way user types are discovered according to the apache configuration changes.
*Added RA/Sponsor in VO as a placeholder to store information for upcoming PKI update.
*Replaced Footprints SOAP API with GOC Ticket REST API.
*Added osg-security-team@OPENSCIENCEGRID.ORG to VO registration form’s CC list.
*Updated stylesheet (bootstrap) and page layouts on various pages.

GOC Ticket 1.51

ITB version is now available for testing at

*Removed http to https forwarding (in preparation for oim v3 style user login system)
*Refactored the way footprints assignees were verified during ticket submission
*Refactored & improved GOC local access checker which does not require specific IP addresses to be configured.
*Added GOC local access test for REST API. Added open and submit APIs
*Fixed various attachment handling issues (removing some characters (#, and &) from the attached file name; increased the maximum file size to 10M; fixed the thumbnail request URL)
*(patched) Fixed the issue that resource/vo fblist on consolidated submitter doesn't repopulate after reload
*(patched) removed unnecessary loading of “careof” feature for non-admin user.

GOC Ticket Synchronizer (GOC-TX) 1.25

Update is scheduled on Wednesday 4/25 during GGUS update at CERN.

ITB version is now available for testing via

*Updated to the latest GGUS WSDL. Removed setStartRecord & setMaxLimit functions

OSG Display

ITB version is now available for testing via

*Updating OSG_Display_Data-1.0.3-2 which improves SQL query performance in order to avoid SQL query pileup issue on the Gratia Db [DISPLAY-7]

All Services

*Updates to RHEL packages will be applied, but this will not require reboots.
*Services which use Tomcat5 will need to be restarted due to a security update, but this should cause only a momentary interruption in service.