PM12630: REDIRECT TO LOGIN PAGE DOES NOT WORK FOR HOSTNAME-BASE VPS

6.1.0.4 Download: WebSphere Portal and WCM V6.1.0 fix pack 4 & 6.1.5 fix pack 1
6.1.0.5 Download: WebSphere Portal and WCM V6.1.0 fix pack 5
6.1.0.6 Download: WebSphere Portal and WCM V6.1.0 fix pack 6
Recommended Updates for WebSphere Portal and Web Content Manager V6.1

APAR status

• Closed as program error.

Error description

• For a hostname-based VPs, it is not possible to trigger the
  login process by accessing a protected page as anonymous user.
  Instead, the user will be redirected to the default page.
  
  The change to the wps.war web.xml file can either be done
  automatically through the following config task
  <wp_profile>/ConfigEngine/ConfigEngine.[bat|sh]
  apply-PM12630
  or manually be exporting the wps.ear, merging the web.xml with
  the changes outlined in the problem solution section and
  redeploying the wps.ear.
  
  Do not use the this task if portal url schema names or servlet
  filters have been modified in wps.war web.xml. In this case,
  the
  change has to be manually merged into the web.xml file to keep
  the prior modifications.
  
  For manual changes, please follow the steps outlined in the
  infocenter:
  - Exporting the portal EAR file
  http://publib.boulder.ibm.com/infocenter/wpdoc/v6r1/topic/com
  .ibm.wp.ent.doc_v615/security/ssl.html
  - execute step 5 - Perform the following steps to export the
  WebSphere Portal EAR file
  - now add the new filter mapping entries to
  wps_expanded/wps.war/WEB-INF/web.xml file
  - finally execute step 8 - Perform the following steps to
  redeploy the WebSphere Portal EAR file
  

Local fix

• As a local workaround, you can manually add the following two
  filter-mappings to wps.war/WEB-INF/web.xml:
  
    <filter-mapping>
       <filter-name>VirtualPortal Filter</filter-name>
       <url-pattern>/redirect/*</url-pattern>
    </filter-mapping>
    <filter-mapping>
       <filter-name>URL Analyzer</filter-name>
       <url-pattern>/redirect/*</url-pattern>
    </filter-mapping>
  
  These two mappings need to be added just above this filter
  mapping:
  
  <filter-mapping>
  <filter-name>Login Redirect</filter-name>
  <url-pattern>/redirect/*</url-pattern>
  </filter-mapping>
  

Problem summary

• For a hostname-based VPs, it is not possible to trigger the
  login process by accessing a protected page as anonymous user.
  Instead, the user will be redirected to the default page.  The
  change to the wps.war web.xml file can either be done
  automatically through the following config task
  
        <wp_profile>/ConfigEngine/ConfigEngine.[bat|sh]
  apply-PM12630
  
  or manually be exporting the wps.ear, merging the web.xml with
  the changes outlined in the problem solution section and
  redeploying the wps.ear.  Do not use the this task if portal url
  schema names or servlet filters have been modified in wps.war
  web.xml. In this case, the change has to be manually merged into
  the web.xml file to keep the prior modifications.   For manual
  changes, please follow the steps outlined in the infocenter:
  
    - exporting the portal EAR file
  http://publib.boulder.ibm.com/infocenter/wpdoc/v6r1/topic/com.ib
  m.wp.ent.doc_v615/security/ssl.html
    - execute step 5 - Perform the following steps to export the
  WebSphere Portal EAR file
    - now add the new filter mapping entries to
  wps_expanded/wps.war/WEB-INF/web.xml file
    - finally execute step 8 - Perform the following steps to
  redeploy the WebSphere Portal EAR file
  

Problem conclusion

• This APAR will add the following two following two
  filter-mappings to wps.war/WEB-INF/web.xml:
  
    <filter-mapping>
       <filter-name>VirtualPortal Filter</filter-name>
       <url-pattern>/redirect/*</url-pattern>
    </filter-mapping>
    <filter-mapping>
       <filter-name>URL Analyzer</filter-name>
       <url-pattern>/redirect/*</url-pattern>
    </filter-mapping>
  
  Failing Module(s):
     Authorization/Authentication (login/logout)
  
  Affected Users:
     All VP users
  
  Version Information:
     Portal Version(s): 6.1.0.3
      Pre-Requisite(s): ---
       Co-Requisite(s): ---
  
  Manuel Steps:
     None
  
  Platform Specific:
     This fix applies to all platforms.
  
  
  PM12630 is part of Cumulative Fix 04 for Portal 6.1.0.3 /
  6.1.5.0.
  
  The Cumulative Fix is available on Fix Central:
  
  http://www.ibm.com/eserver/support/fixes/fixcentral/swgquickorde
  r?apar=PM11273&productid=WebSphere%20Portal&brandid=5
  

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

  WEBSPHERE PORTA

• Fixed component ID

  5724E7600

Applicable component levels

• R61C PSY

     UP