PK78677: ALLOW LOGIN WHEN REPOSITORIES ARE DOWN

Java SDK 1.5 SR10 Cumulative Fix for WebSphere Application Server
6.1.0.31: Java SDK 1.5 SR11 FP1 Cumulative Fix for WebSphere Application Server
6.1.0.33: Java SDK 1.5 SR12 FP1 Cumulative Fix for WebSphere
6.1.0.29: Java SDK 1.5 SR11 Cumulative Fix for WebSphere Application Server
6.1.0.35: Java SDK 1.5 SR12 FP2 Cumulative Fix for WebSphere
6.1.0.37: Java SDK 1.5 SR12 FP3 Cumulative Fix for WebSphere
6.1.0.39: Java SDK 1.5 SR12 FP4 Cumulative Fix for WebSphere Application Server
6.1.0.41: Java SDK 1.5 SR12 FP5 Cumulative Fix for WebSphere Application Server
6.1.0.43: Java SDK 1.5 SR13 Cumulative Fix for WebSphere Application Server
6.1.0.45: Java SDK 1.5 SR14 Cumulative Fix for WebSphere Application Server
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
6.1.0.47: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server

APAR status

• Closed as program error.

Error description

• Problem:
  
  In order to use WebSphere Application Server V6.1 federated
  repositories functionality, ALL of the configured
  repositories, which are specified as part of the federated
  repository configuration (for example LDAP ), MUST be
  active. This causes the following 2 problems.
  (1) When one of the configured repositories is down,  you
  cannot start or stop the WebSphere Application Server
  AppServer process even if another repository is active and a
  user will be found in that repository.
  (2) When one of the configured repositories is down after the
  WebSphere Application Server AppServer process started,
  authentication will fail even if another repository is active
  and user will be found in that repository.
  
  Requirement:
  When one of the configured repositories is down, the federated
  repository should work with other active repositories.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of WebSphere Application Server   *
  *                  V6.1                                        *
  ****************************************************************
  * PROBLEM DESCRIPTION: Allow login when repositories are down  *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  In order to use WebSphere Application Server V6.1 federated
  repositories functionality, ALL of the configured
  repositories, which are specified as part of the federated
  repository configuration MUST be active.
  

Problem conclusion

• With this feature, when one of the configured repositories is
  down, the federated repository should work with other active
  repositories.
  
  A new config parameter has been added to these CLIs:
  createIdMgrRealm
  updateIdMgrRealm
  
  Parameter:
  
  -allowOperationIfReposDown
  Specifies whether the system allows a repository operation
  such as get or search to complete successfully, even if
  repositories in the realm are down. The default value is
  false. (Boolean, optional)
  
  The command is fully documented for Websphere Application
  Server 7, at this link (doc defect #571019):
  http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/topic/com.
  ibm.websphere.web20fep.multiplatform.doc/info/ae/ae/rxml_atidmgr
  realmconfig.html
  
  
  The fix for this APAR is currently targeted for inclusion in
  fixpack 6.1.0.23.  Please refer to the Recommended
  Updates page for delivery information:
  http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
  

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

  WEBS APP SERV N

• Fixed component ID

  5724H8800

Applicable component levels

• R61A PSY

     UP

• R61H PSY

     UP

• R61I PSY

     UP

• R61P PSY

     UP

• R61S PSY

     UP

• R61W PSY

     UP

• R61Z PSY

     UP