Domain: Security: General
Configuration Options Advanced Configuration Options Related Tasks Related Topics
This page allows you to define the general security settings for this WebLogic Server domain. Use this page to change the default security realm for the WebLogic domain.
Name Description Default Realm
Select the security realm that should be used as the default (active) realm for this WebLogic Server domain.
All available security realms are listed on the pull-down menu. If you configure a new security realm, but do not configure any security providers or all the required security providers, the security realm will not be available from the pull-down menu. In order for a security realm to be valid, you must configure an Authentication provider, an Authorization provider, an Adjudication provider, a Credential Mapping provider, and a Role Mapping provider.
Anonymous Admin Lookup Enabled
Specifies whether anonymous, read-only access to WebLogic Server MBeans should be allowed from the
With anonymous access enabled, you can see the value of any MBean attribute that is not explicitly marked as protected by the WebLogic Server MBean authorization process. This attribute should be enabled only for backward compatibility.
Cross Domain Security Enabled
Specifies whether or not cross-domain security is enabled for the domain.
If you enable cross-domain security, you need to add one or more cross-domain users and specify a credential mapping that includes the credentials for each remote domain user that is authorized to access this domain.
Excluded Domain Names
Specifies a list of remote domain names that are to be excluded from the cross-domain checks.
The list can either be semicolon-separated domain names on the same line or could be one domain name per line or could be a combination of both.
Advanced Configuration Options
Name Description Security Interoperability Mode
Specifies the security mode of the communication channel used for XA calls between servers that participate in a global transaction. All server instances in a domain must have the same security mode setting.
Security Interoperability Mode options:
The transaction coordinator makes calls using the kernel identity over an admin channel if it is enabled, and
anonymousotherwise. Man-in-the-middle attacks are possible if the admin channel is not enabled.
The transaction coordinator makes calls using
anonymousat all times. This implies a security risk since a malicious third party could then try to affect the outcome of transactions using a man-in-the-middle attack.
The transaction coordinator makes calls as the kernel identity over an insecure channel. This is a high security risk because a successful man-in-the-middle attack would allow the attacker to gain administrative control over both domains. This setting should only be used when strong network security is in place.
The credential for this WebLogic Server domain. When a domain is created, a unique credential is generated for the domain. If you want to establish trust between two or more domains, decide on a credential that will be shared by the domains, then specify it here and in the other domains.
The user name that the Administration Server uses to communicate with Node Manager when starting, stopping, or restarting Managed Servers.
The password that the Administration Server uses to communicate with Node Manager when starting, stopping, or restarting Managed Servers.
When you get the value of this attribute, WebLogic Server does the following:
Retrieves the value of the
Decrypts the value and returns the unencrypted password as a String.
When you set the value of this attribute, WebLogic Server does the following:
Encrypts the value.
Sets the value of the
NodeManagerPasswordEncryptedattribute to the encrypted value.
Using this attribute (
NodeManagerPassword) is a potential security risk because the String object (which contains the unencrypted password) remains in the JVM's memory until garbage collection removes it and the memory is reallocated. Depending on how memory is allocated in the JVM, a significant amount of time could pass before this unencrypted data is removed from memory.
Instead of using this attribute, you should use
Web App Files Case Insensitive
Specifies the case sensitive URL-pattern matching behavior for security-constraints, servlets, filters, virtual-hosts, etc. in the webapp container and external security policies. LegalValues: "os", "true", "false".
When the value is set to "os", the pattern matching is case sensitive on all platforms except windows file system. Note that on non-Windows file system WebLogic Server doesn't enforce case sensitivity and relies on the file system for optimization. As a result, if you have a Windows Samba mount from UNIX or Mac OS that have been installed in case-insensitive mode, there is a chance of a security risk. If so, specify case insensitive lookups by setting this attribute to
true. This property also preserves backward compatibility on Windows file systems. Releases prior to WebLogic Server 9.0, are case insensitive on Windows. Starting with WebLogic Server 9.0, URL-pattern matching is strictly enforced. During the upgrade of older domains, the value of this parameter is explicitly set to "os" by the upgrade plug-in to preserve backward compatibility.
Enforce Strict URL Pattern
Specifies whether the system should enforce strict URL pattern., " / " to represent the entire contents of a Web Application.
This property is provided for backward compatibility with version 8.1. When this field is checked the system enforces the use of the " / " character as the default representation of an entire Web application in the security container. This is the standard J2EE syntax and is consistent with the syntax used by the Servlet container. In version 8.1 the security container used " /* " as the default representation of an entire Web application. If you want your applications to continue to use " /* " in this context you must change the value to false (unchecked). When set to false, the security container recognizes " /* " as the equivalent of " / " , thereby ensuring consistency with the Servlet container.
Downgrade Untrusted Principals
Specifies whether to downgrade to anonymous principals that cannot be verified.
This feature is useful for server-server communication between untrusted domains.
Principal Equals Case Insensitive
Specifies whether the WebLogic Server principal name is compared using a case insensitive match when the equals method for the principal object is performed.
If this attribute is enabled, matches are case insensitive.
Note: This attribute applies
Principal Equals Compare DN and GUID
Specifies whether the GUID and DN data in a WebLogic Server principal object are used when the equals method of that object is invoked.
If enabled, the GUID and DN data (if included among the attributes in a WebLogic Server principal object) and the principal name are compared when this method is invoked.
Compatibility Connection Filters Enabled
Specifies whether this WebLogic Server domain enables compatibility with previous connection filters.
Checking or unchecking this fields changes the protocols names used when filtering needs to be performed.
Allow Security Management Operations if Non-dynamic Changes have been Made
Specifies whether security management operations are allowed if non-dynamic changes have been made and the Admin Server requires restart.
If a user makes changes to non-dynamic attributes of security MBeans and then activates the changes, by default he can not perform any security management operations until the server has been restarted. You can override this default behavior by checking this field. This permits users to perform security management operations without restarting the server. Note that this attribute is reset to false when a new console session starts.
- Configure new security realms
- Change the default security realm
- Enable Cross Domain Security between domains
- Create a Cross-Domain Security Credential Mapping
- Reset the EnforceStrictURLPattern flag