1.2 Common Proxy Install Issues

Starting with OES 2 SP3, when you install a new server, you can create a proxy user that can cover multiple OES services. For more information, see Common Proxy User - New in SP3 in the OES 2 SP3: Planning and Implementation Guide.

The following are known issues with the common proxy user:

1.2.1 The OES Common Proxy User Password Is Not Always Compliant with the Password Policies

If you have password policies that support non-ASCII passwords or that require passwords to be 4 characters or shorter or 12 characters or longer , make sure you select the Attach common proxy user to common proxy policy option (the default setting) in the OES proxy install screen.

This prevents password-compliance issues with the proxy user after installation.

If you are installing, then abort the installation and reinstall OES. In the common proxy page, you must provide a password for the common proxy user that complies with your password policy.

1.2.2 New Container Creation Not Possible During a New Install

The eDirectory container for the common proxy user cannot be created at the same time as the user object.

In the OES install, when you specify the admin user, and again when you specify the container for the server object, you can automatically create new eDirectory containers by editing the path in the install page.

The path to the common proxy user is also editable, but it is not processed by the install like the server and admin user paths. The path to the common proxy user must be one of the following:

  • A path to a container that is specified for either the server or the eDirectory Admin user. (The default for the common proxy user is the server container path.)

  • A container that already exists in eDirectory if you are installing into an existing tree.

If you attempt to create a new container for the common proxy user by specifying a path that doesn’t meet one of these requirements, the installation program appears to proceed normally until the eDirectory configuration (ndsconfig) runs. At that point the installation fails with an Error creating Common Proxy User: 32 message, and you must start the server installation again, making sure that the container meets one of the requirements stated above.

Novell plans to address this issue in a future OES release.

1.2.3 Installing on a Non-Replica Server Generates an Attach Proxy User To Policy Error

If the server you are creating a common proxy user on is the fourth or later server in your tree, by default it does not have an eDirectory replica. As a result, when the install attempts to attach the proxy user to the proxy policy, the operation fails. YaST throws an error indicating Unable to attach the proxy policy to common proxy user now.

Use iManager to complete the task:

  1. Click OK to close the error notification and complete the installation.

  2. Attach the common proxy user to the Common_Proxy_Policy:

    1. Log into iManager as an eDirectory admin user.

    2. On the Roles and Tasks page, click Passwords > Password Policies.

    3. Click Common_Proxy_Policy.

    4. Click the Policy Assignment tab.

    5. In the Assign to field, browse to the Common Proxy User object and click OK.

    6. Click Apply > OK.

Novell plans to address this issue in a future OES release.