Deleting the realm base entry on i5/OS

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 task, from the profile_root/ConfigEngine directory, to list the base entries for a specific realm.
   • Edit wkplc.properties, located in the profile_root/ConfigEngine/properties directory.

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

   • Save changes to wkplc.properties.

   • Run...
     ConfigEngine.sh wp-delete-realm-baseentry -DWasPassword=password task, from the profile_root/ConfigEngine directory, to delete a base entry from a realm configuration.
     • Propagate the security changes:

       Option	Description
       Standalone	stopServer server1 -username admin_userid -password admin_password ...from... profile_root/bin stopServer WebSphere_Portal -username admin_userid -password admin_password ...from... profile_root/bin startServer server1 ...from... profile_root/bin startServer WebSphere_Portal ...from... profile_root/bin
       Cluster	stopManager-username admin_userid -password admin_password, from the DMGR_PROFILE/bin stopNode -username admin_userid -password admin_password from the profile_root/bin directory stopServer WebSphere_Portal -username admin_userid -password admin_password ...from... profile_root/bin startManager, from the DMGR_PROFILE/bin startNode ...from... profile_root/bin startServer WebSphere_Portal ...from... profile_root/bin

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 i5/OS

Related tasks

Enable LDAP security after cluster creation

---