Create new multiple security domains


Overview

We can create multiple security domains in the configuration. By creating multiple security domains, we can configure different security attributes for admin and user applications within a cell environment.

Only users assigned to the administrator role can create new multiple security domains.

Enable global security in the environment before creating new multiple security domains.

Security domains provide a mechanism to use different security settings for admin applications and user applications. They also provide the ability to support multiple security settings so different applications can use different security attributes like user registry or login configurations. Use multiple security domains to achieve the following goals:


Create a new security domain

  1. Click Security > Security domains.

  2. On the Security domains collection page, click New.

  3. Specify a unique name for the domain. A domain name must be unique within a cell and cannot contain an invalid character. This field is required.

  4. Specify a unique description for the domain. After you click Apply we are returned to the Security domains detail page

  5. Under Assigned Scopes, assign the security domain to the entire cell or select the specific servers, clusters, and service integration buses to include in the security domain.

  6. Customize the security configuration by specifying security attributes for the new domain and by assigning it to cell resources. You can change security attributes such as the following:

    Application Security

    Settings for application security and Java2 security. Use the global security settings or customize the settings for a domain.

    Select Enable application security to enable or disable security this choice for user applications. When this selection is disabled, all of the EJBs and Web apps in the security domain are no longer protected. Access is granted to these resources without user authentication. When you enable this selection, the J2EE security is enforced for all of the EJBs and Web apps in the security domain.

    J2EE security is only enforced when Global Security is enabled in the global security configuration, (that is, we cannot enable application security without first enabling Global Security at the global level).

    Java 2 Security

    Select Java 2 security to enable or disable Java 2 security at the domain level. This choice enables or disables Java 2 security at the process (JVM) level so that all applications (both administrative and user) can enable or disable Java 2 security.

    User realm

    This section enables you to configure the user registry for the security domain. We can separately configure any registry except the federated registry used at the domain level. The federated repository can only be configured at the global level but can be used at the domain level. Read about Multiple security domains for more information.

    Trust association

    When you configure the TAI at a domain level, the interceptors configured at the global level are copied to the domain level for convenience. We can modify the interceptor list at the domain level to fit the needs. Only configure those interceptors that are to be used at the domain level.

    SPNEGO Web Authentication

    The SPNEGO Web authentication, which enables you to configure SPNEGO for Web resource authentication, can be configured at the domain level.

    In WAS V6.1, a TAI that uses the SPNEGO to securely negotiate and authenticate HTTP requests for secured resources was introduced. In WAS 7.0, this function is now deprecated. SPNEGO Web authentication has taken its place to provide dynamic reload of the SPNEGO filters and to enable fallback to the application login method.

    RMI/IIOP Security

    The RMI/IIOP security attribute refers to the CSIv2 (Common Secure Interoperability version 2) protocol properties. When you configure these attributes at the domain level, the RMI/IIOP security configuration at the global level is copied for convenience.

    We can change the attributes that need to be different at the domain level. The Transport layer settings for CSIv2 inbound communications should be the same for both the global and the domain levels. If they are different, the domain level attributes are applied to all of the application in the process.

    JAAS application logins

    Configuration settings for the JAAS application logins. Use the global security settings or customize the settings for a domain.

    You can configure the following data aliases at the domain level.

    1. JAAS application logins
    2. JAAS system logins
    3. JAAS J2C authentication

    By default, all of the applications in the system have access to the JAAS logins configured at the global level. The security runtime first checks for the JAAS logins at the domain level. If it does not find them, it then checks for them in the global security configuration. Configure any of these JAAS logins at a domain only when specify a login used exclusively by the applications in the security domain.

    JAAS system logins

    Configuration settings for the JAAS system logins. We can use the global security settings or customize the settings for a domain.

    The following data aliases can be configured at the domain level.

    1. JAAS application logins
    2. JAAS system logins
    3. JAAS J2C authentication

    By default, all of the applications in the system have access to the JAAS logins configured at the global level. The security runtime first checks for the JAAS logins at the domain level. If it does not find them, it then checks for them in the global security configuration.

    Set these JAAS logins in a domain when specifying a login used exclusively by the applications in the security domain.

    JAAS J2C authentication

    Configuration settings for the JAAS J2C authentication data. Use the global security settings or customize the settings for a domain.

    The following data aliases can be configured at the domain level.

    1. JAAS application logins
    2. JAAS system logins
    3. JAAS J2C authentication

    By default, all of the applications in the system have access to the JAAS logins configured at the global level. The security runtime first checks for the JAAS logins at the domain level. If it does not find them, it then checks for them in the global security configuration. Set any of these JAAS logins at a domain only when specify a login used exclusively by the applications in the security domain.

    Authentication Mechanism Attributes

    Various cache settings that need to applied at the domain level.

    Select Authentication cache settings to specify the authentication cache settings. The configuration specified on this panel is applied only to this domain.

    Select LTPA Timeout to configure a different LTPA timeout value at the domain level. The default timeout value is 120 minutes, which is set at the global level. If the LTPA timeout is set at the domain level, any token that is created in the security domain when accessing user applications is created with this expiration time.

    When Use realm-qualified user names is enabled, user names returned by methods such as getUserPrincipal( ) are qualified with the security realm (user registry) used by applications in the security domain.

    Authorization Provider

    Configure an external third party JACC (Java Authorization Contract for Containers) provider at the domain level. TAM’s JACC provider can only be configured at the global level. Security domains can still use it if they do not override the authorization provider with another JACC provider or with the built-in native authorization.

    Custom properties

    Set custom properties at the domain level that are either new or different from those at the global level. By default, all of the custom properties at the global security configuration can be accessed by all of the applications in the cell. The security runtime code first checks for the custom property at the domain level. If it does not find it, it then attempts to obtain the custom property from the global security configuration.

  7. Click Apply.

  8. After we have saved the configuration changes, restart the server for the changes to take effect.

 

Related concepts


Multiple security domains

 

Related tasks


Delete multiple security domains
Copy multiple security domains
Set inbound trusted realms for multiple security domains
Set security domains using scripting
Set multiple security domains using scripting
Remove security domains using scripting
Mapping resources to security domains using scripting
Set multiple security domains

 

Related


Administrative roles