PK73830: WP-MODIFY-FEDERATED-SECURITY FAILS USING CURRENT INSTRUCTIONS

APAR status

• Closed as documentation error.

Error description

• When following the instructions located in the WebSphere Portal
  6.1 Information Center:
  
  http://publib.boulder.ibm.com/infocenter/wpdoc/v6r1m0/index.jsp?
  topic=/com.ibm.wp.ent.doc/security/win_mod_fed_sec.html
  
  step #4 will fail with the following:
  
  
  BUILD FAILED
  E:\ibm\wp_profile\ConfigEngine\config\actions\wp_security_pub.xm
  l:66: The following error occurred while executing this line:
  E:\ibm\wp_profile\ConfigEngine\config\actions\wp_security_intern
  al.xml:66: Given user '<value from federated.primaryAdminId in
  wkplc.properties>' does not exist.
  

Local fix

• Stop server1 and WebSphere Portal.  Then run the command:
  
  ConfigEngine wp-modify-federated-security
  -DWasPassword=<password> -Dskip.ldap.validation=true
  
  This will cause the task to run in local mode rather than
  against the server.
  

Problem summary

• When following the instructions located in the WebSphere Portal
  6.1 Information Center:
  
  http://publib.boulder.ibm.com/infocenter/wpdoc/v6r1m0/index.jsp?
  topic=/com.ibm.wp.ent.doc/security/win_mod_fed_sec.html
  
  step #4 will fail.
  

Problem conclusion

• WebSphere Portal Information Center 6.1.0 was updated with the
  modified step:
  
  Run the ConfigEngine.bat wp-modify-federated-security
  -DWasPassword=password -Dskip.ldap.validation=true task, from
  the wp_profile_root\ConfigEngine directory, to change the
  configuration to use a federated repository.
  

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

Applicable component levels