Standalone server: Configure Portal to use a user registry
A user registry prevents unauthorized access to the server and protects the data.
- Prerequisites
- Standalone server: Configure databases
Make a backup of the portal configuration; see backupConfig command for information.
- Prerequisites
- Standalone server: Configure databases
Select the operating system of the server where you have the user registry installed.
- Standalone server: Prepare a SecureWay Security Server
- Standalone server: Choose the user registry model on z/OS
Choose between securing IBM WebSphere Portal with a standalone LDAP user registry or by adding LDAP user registries and/or database user registries to the default federated repository. Choose the federated repository if you plan to enable the transient user feature.- Standalone server: Adapt the attribute configuration
After installing IBM WebSphere Portal and configuring the LDAP user registries, adapt the attribute configuration to match the configured LDAP server(s) and the business needs.- Standalone server: Configure Portal to use dynamic groups on z/OS
By default, WebSphere Portal is enabled for static groups. However, the Virtual Member Manager (VMM) allows users to be members of either static or dynamic groups. Static groups are those where a persistent binding exists between a group and its members. Dynamic groups are those where a search query is defined to retrieve the members of a group. If you have the LDAP server configured to use dynamic groups, complete the steps in this task for WebSphere Portal to use dynamic group queries when you setup the LDAP server.- Standalone server: Enable referrals for the LDAP user registry on z/OS
Referrals redirect object requests from one LDAP server to another when objects do not exist or cannot be located in a particular directory tree. You should enable referrals if the environment has more than one user registry existing on multiple servers or domains.
Parent: Set up a stand-alone server on z/OS
Previous: Standalone server: Prepare a remote Web server when portal is installed on z/OS
Related: