Banner Password Synchronization works for Macintosh users

The login page for Banner Forms was changed early on 5/15/2009 (see Cascade middle tier http server restarted), so Banner Forms users are prompted for Puget Sound username and password instead of Banner Database username, password, and database name.

Initially, this did not work correctly for Macintosh users, who were required to enter their username and password twice.

This problem was resolved Saturday morning, so Macintosh users should now be able to log in to Banner Forms (and create purchase orders), entering their Puget Sound credentials only one time per session.

To fix the problem, Ed changed parameter baseHTML to point to our modified basejpisso_webutil.htm file.

Cascade middle tier http server restarted

As part of implementing Banner Password Synchronization, the Cascade middle tier http server was restarted so that the following change in the httpd.conf file would take effect:

#Redirect /banner https://psforms.ups.edu/forms/frmservlet?config=banner
Redirect /banner https://psforms.ups.edu/banner_sso/gokssso.p_login

This directs cascade.ups.edu/banner to the new Banner login page that authenticates against OID.

See also Banner Password Synchronization works for Macintosh users

Mac/Safari upgrade works with Cascade – Technical Help updated

The recently released Mac OS X 10.5.7 and Safari 3.2.3 fix the problem where users received “Too many redirects” error when logging in to Cascade Web.

The Technical Help page has been updated to show which versions of Mac OS X and Safari are compatible with Cascade. Browser/OS combinations that are not compatible still receive a message that includes a link to this Technical Help page.

Cascade users are now warned if using incompatible browser

A person using a Web Browser that is not compatible with Cascade Web now sees a warning message before entering their username and password and encountering an error. At present, a person attempting to log into Cascade Web from Mac OSX 10.5.6 using Safari 3.1.2, 3.2.1, or 4.0 beta will see the following log-in page:

Screenshot of message, "Please use a different Web browser."

Test Partner Application reestablished after Summit refresh

The OID schema on summit was inadvertently overwritten with Cascade’s OID schema during a refresh of Summit. This required re-registering the partner application for “/summit”. This did not work until we dropped oid.wwsec_enabler_config_info$ then executed @loadsdk from albert’s oracle account.

The listener_token value is: cascadetest.ups.edu:4445

Messages Quarantined Before 9:00 AM Unavailable on Web 4/27/2009

Spam messages quarantined prior to 9:00 AM on April 27, 2009, are no longer available on the PureMessage Web site due to the domain name change which took effect at that time. Messages arriving after 9:00 AM will be available as usual.

If you need messages quarantined before this time, please contact the HelpDesk at helpdesk@ups.edu or x8585.

[Completed] E-mail Addresses and URLS Updated in Cascade 4/27/2009

As part of the domain change project, e-mail addresses and URLs stored in the Cascade database have been updated from “ups.edu” to “pugetsound.edu”. New account provisioning has also been updated accordingly.

The directory and most web applications display the new addresses and URLs. A few remaining Web applications will be changed in the coming week.

Whidbey certificate expired but purposely not renewed

I have the valid certificate ready but not installed for the following reasons.

  1. There should be no known application using the Certificate.
  2. In the past, the Certificate has been renewed, not knowing it’s used or not, just for the precaution.
  3. Before not renewing anymore, I need to make sure the Certificate is not really used by any of the applications.