Clusters and security - Scenarios

Prior to federating portal nodes into the cell, the portal administrator group and user, for example, wpsadmins and wpsadmin, must be defined in the dmgr's security repository.

Using the WAS admin console to configure out-of-box security is NOT supported in a portal stand-alone environment. Configuring security IS supported in a clustered environment that uses the dmgr console.

Modified security with VMM federated

When the existing dmgr cell has already modified its default security setting prior to the node joining the cell, portal supports the capability of using two different sets of admin user ID and password credentials when federating a node into a cell..

• one set for the node authentication
• one set for dmgr authentication

It is not necessary to define a common admin user ID before portal joins the cell. If the dmgr cell is using federated VMM with additional repositories, the security settings on the Portal node are replaced with the modified dmgr VMM federated security settings. The original stand-alone environment security settings are preserved and revert back to the original settings if we remove the node from the cluster.

Modified security with standalone LDAP server

If the dmgr cell is using standalone LDAP security, configure the LDAP values into the portal property files before federation. This enables portal to dynamically adapt to the existing standalone LDAP security settings of the cell. Once the cluster has been set up, security changes to the dmgr cell security settings can be made using the portal security tasks.

Parent: Cluster considerations