Primary administrative user name
Specifies the name of the user with administrative privileges that is defined in the repository, for example, adminUser.
Use this page to manage the realm. The realm can consist of identities in the file-based repository that is built into the system, in one or more external repositories, or in both the built-in, file-based repository and one or more external repositories.
When you finish adding or updating your federated repository configuration, go to the Apply to validate the changes.
panel and clickA single built-in, file-based repository is built into the system and included in the realm by default.
You can configure one or more Lightweight Directory Access Protocol (LDAP) repositories to store identities in the realm. Click Add base entry to realm to specify a repository configuration and a base entry into the realm. You can configure multiple different base entries into the same repository.
WebSphere® Application Server Version 7.0 distinguishes between the user identities for administrators who manage the environment and server identities for authenticating server to server communications. In most cases, server identities are automatically generated and are not stored in a repository.
However, if you
are adding a previous version node to the latest version cell and the previous version node used a
server identity and password, you must ensure that the server identity and password for the previous
version are defined in the repository for this cell. Enter the server user identity and password on
this panel.
Specifies the name of the realm. You can change the realm name, but you should complete any other federated repository configuration steps prior to making this change.
Specifies the name of the user with administrative privileges that is defined in the repository, for example, adminUser.
Enables the application server to generate the server identity, which is recommended for environments that contain only Version 6.1 or later nodes. Automatically generated server identities are not stored in a user repository.
Information | Value |
---|---|
Default: | Enabled |
Specifies a user identity in the repository that is used for internal process communication. Cells that contain Version 6.1 or later nodes require a server user identity that is defined in the active user repository.
Information | Value |
---|---|
Default: | Enabled |
Specifies the user identity that is associated with the z/OS system started task. Each controller and server can have its own identity.
Specifies the user ID that is used to run the application server for security purposes.
Specifies the password that corresponds to the server ID.
Specifies that a case-insensitive authorization check is performed.
If case sensitivity is not a consideration for authorization, enable the Ignore case for authorization option.
Specifies whether operations (such as login, search, or get) are allowed even if the repositories in the realm are down.
Sets the global schema option for the data model in a multiple security domain environment. Global schema refers to the schema of the admin domain.
Specifies the base entry within the realm. This entry and its descendents are part of the realm.
Specifies a unique identifier for the repository. This identifier uniquely identifies the repository within the cell.
Specifies the repository type, such as File or LDAP.