Using option '-Dskip.ldap.validation=true' to avoid ConfigEngine failure

Technote (troubleshooting)


Problem


Certain configuration tasks may fail with the following error:

BUILD FAILED

C:\IBM\WebSphere61\wp_profile\ConfigEngine\config\actions\wp_security_pub.xml:2169: The following error occurred while executing this line:

C:\IBM\WebSphere61\wp_profile\ConfigEngine\config\actions\wp_security_internal.xml:66: Given user 'uid=wpsadmin,ou=people,o=ibm.com' does not exist.

Resolving the problem


Various configuration tasks call the sub-task, wp-validate-user-exists, including:


    wp-change-was-admin-user
    wp-change-portal-admin-user
    wp-modify-federated-security

Due to various reasons, the task can fail. In most cases, you can skip the validation step by
adding -Dskip.ldap.validation=true on the command line, because the users and groups are already validated during security configuration tasks. Note this parameter turns off many sanity checks and should only be used if other troubleshooting methods have been exhausted.

The following example shows how to use the parameter:
    ConfigEngine.bat -DnewAdminId=<wasadminDN>
    -DnewAdminPwd=<password> -Dskip.ldap.validation=true wp-change-was-admin-user


Rate this page:

(0 users)Average rating

Document information


More support for:

WebSphere Portal
Security

Software version:

6.1, 7.0, 8.0

Operating system(s):

AIX, HP-UX, Linux, Solaris, Windows, i5/OS, z/OS

Software edition:

Enable, Express, Extend, Server

Reference #:

1376008

Modified date:

2013-05-09

Translate my page

Machine Translation

Content navigation