PM33124: Console redirect fails when accessing console via login page under Internet Explorer

APAR status

• Closed as program error.

Error description

• When attempting to access the Build Forge console under
  Microsoft Internet Explorer via the login page directly, users
  are not redirecting to the console as expected.
  Users instead are redirected to an error indicating 'The page
  cannot be displayed'.
  
  Steps to reproduce:
  
  - Access Build Forge console via login page directly.
  ie: https://bfconsole:8443/rbf-services/login.jsp
  
  - Login to Build Forge console normally.
  
  Expected result:
  
  User is redirected to the console front page.
  
  Actual result:
  
  User is redirected to the error indicating 'The page cannot be
  displayed' under the AuthServlet rbf-services page.
  
  https://bfconsole:8443/rbf-services/AuthServlet
  
  Workaround:
  
  Access the Build Forge console directly under the Apache
  address.
  
  ie:
  http://bfconsole
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Symptom:
  Console redirect goes to https://host when the user
  initially browses to the Tomcat port https://host:8443
  
  Cause:
  The redirect code is designed to handle the user coming from
  http://host as that is what it expects. When a user browses
  directly to https://host:8443 the referer context is not
  present so the UI has to guess. The guess simple strips off
  the port association and the redirect URL becomes
  https://host. In most installations the Apache portion is
  not set up for SSL and as such https://host is unreachable.
  

Problem conclusion

• Fix:
  The referer cookie code was modified to handle the
  previously stated use case. The referal URL is created by
  the first of the following steps which passes:
  1) query string from the referring page
   This exists only if the user goes first to the
  Apache hosted BF page such as http://host
  2) bfreferer cookie
   This exists only if the user
  3) Admin ? System ? Console URL
   This entry is required if the URL is _not_
  http://host. Otherwise the fallback will go to the wrong
  place.
  4) fallback to http://host
   This is the last resort. If the referer, cookie,
  _and_ console URL were not set the SL has to guess that the
  Apache BF location if the current host on port 80 as this is
  the default configuration - http://host
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  BUILD FORGE SE

• Fixed component ID

  5724S2705

Applicable component levels

• R711 PSN

     UP