Deleting the realm base entry on Solaris

If you made changes to your realm and no longer require the base entry that created for the realm, you can delete it.

In a single server environment the WebSphere_Portal and server1 servers can be either stopped or started.

In a clustered environment stop all appservers on the system including WebSphere_Portal and server1 and then start the nodeagent and deployment manager servers before starting the following task.

To delete the realm base entry:

If you delete a base entry from the default realm, then users belonging to that base entry will no longer be able to log in, even on other realms that still contain the base entry. Therefore, the default realm should contain all the base entries for all active realms.

1. Edit...
   profile_root/ConfigEngine/properties/wkplc.properties

2. For realmName, type the name of the realm that you want to query.

3. Save changes to wkplc.properties.

4. Run...
   ./ConfigEngine.sh wp-query-realm-baseentry -DWasPassword=password

   from the profile_root/ConfigEngine directory, to list the base entries for a specific realm.

5. Edit wkplc.properties, located in the profile_root/ConfigEngine/properties directory.

6. Enter a value for the following parameters under the VMM realm configuration heading:
   • realmName
   • deleteBaseEntry

7. Save changes to wkplc.properties.

8. Run...
   ./ConfigEngine.sh wp-delete-realm-baseentry -DWasPassword=password

   from the profile_root/ConfigEngine directory, to delete a base entry from a realm configuration.

9. Propagate the security changes:

   Option	Description
   Standalone	cd profile_root/bin ./stopServer.sh server1 -username admin_userid -password admin_password ./stopServer.sh WebSphere_Portal -username admin_userid -password admin_password ./startServer.sh server1 ./startServer.sh WebSphere_Portal
   Cluster	cd dmgr_profile/bin ./stopManager.sh-username admin_userid -password admin_password cd profile_root/bin ./stopNode.sh -username admin_userid -password admin_password ./stopServer.sh WebSphere_Portal -username admin_userid -password admin_password cd dmgr_profile/bin ./startManager.sh cd profile_root/bin ./startNode.sh ./startServer.sh WebSphere_Portal

If you performed these steps after creating the clustered environment, run enable-jcr-security on the secondary node.

Parent topic:

Deleting the user registry configurations on Solaris

Related tasks

Enable LDAP security after cluster creation

---