380539 - Premier America Credit Union Web Site Blocks Login from SeaMonkey

Status: RESOLVED WORKSFORME

(Tech Evangelism Graveyard :: English US, defect)

Description

[David E. Ross]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.2) Gecko/20070222 SeaMonkey/1.1.1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.2) Gecko/20070222 SeaMonkey/1.1.1

Start at home page:  <http://www.premier.org/>.  

Select "Home banking", getting "Home Banking log in" page.  Enter user ID and password.  Select Log In button.  

Get "Error #1514".  Select "here" link in "Click here for more information."  Get "ONLINE HELP INDEX" in a new tab (available only if a valid ID and password had been entered, requested a new window).  

Under "UNABLE TO LOG-ON TO INTERNET BANKING", see "This Web site is designed for Netscape® 7.2 or Microsoft® Internet Explorer 7.0 or Mozilla Firefox 1.0 or Safari 1.2 for Macintosh."  Under "Mozilla Firefox v1.0 Settings", see instructions to enable all cookies from all sources, enable images from all sources, enable popups from all sources, and enable Java and JavaScript.  

Close "ONLINE HELP INDEX" tab.  Select Back button on SeaMonkey toolbar to return to "Home Banking log in" page.  Change UA to Firefox 2.0.  Remove all www.premier.org cookies (which were session-only although the instructions were to enable persistent cookies).  Clear cache.  Enable all popups.  Enter user ID and password.  Select Log In button.  

Again get "Error #1514".  Again, select "here" link in "Click here for more information."  Close "ONLINE HELP INDEX" tab.  Select Back button on SeaMonkey toolbar to return to "Home Banking log in" page.  Now, I can login, spoofing Firefox 2.0 without even bothering to remove any cookies.  Note that I never enabled cookies from all sources, leaving my preferences set to enable for cookies only from the originating Website.  

Reproducible: Sometimes

Comment 1

[David E. Ross]

Either Premier America CU fixed the problem, or else they reverted back to a prior version of their Web site.  The problem no longer exists.  Resolving as WorksForMe.