Use this page to understand the predefined custom properties that are related to security.
To view this administrative console page, click Security > Secure administration, applications, and infrastructure > Custom properties. You can click New to add a new custom property and its associated value.
This property is used by the auditing service that was introduced as a technical preview in Version 6. The auditing functionality is not available. Do not modify this property.
Default | REQUIRED |
This property is used by the auditing service that was introduced as a technical preview in Version 6. The auditing functionality is not available. Do not modify this property.
Default | 5000 |
This property is used by the auditing service that was introduced as a technical preview in Version 6. The auditing functionality is not available. Do not modify this property.
Default | false |
This property is used by the auditing service that was introduced as a technical preview in Version 6. The auditing functionality is not available. Do not modify this property.
Default | J2EE=AUTHN=failure=enabled:J2EE=AUTHZ=failure=enabled |
This property completely disables the caller list and will not allow the caller list to change. This property prevents the creation of multiple sessions.
Default | false |
This property allows local comm data to be used as authentication material for the CSIv2 transport layer when the user registry is not a LocalOS user registry.
When this property is set to true, the data retrieved from the local comm transport corresponds to the ASID of the local client connecting to a WebSphere Application Server process. A user corresponding to the ASID must exist in the user registry. When a CSIv2 Establish Message is received by a WebSphere Application Server process and Identity Assertion is requested, the data retrieved from the local comm transport can be used to validate that the client has permission to assert the user specified in the Identity Token in the Attribute Layer. If the user represented by the received ASID is in the Trusted Identities list on the CSIv2 Inbound Authentication page in the administrative console, then that ID is able to assert the Identity Token.
Default | false |
This property will not allow the caller list to change and thus prevent the creation of multiple session entries. This property specifically limits the caller list to the first caller only.
Default | false |
This property specifies the Java Authentication and Authorization Service (JAAS) login configuration that is used for Remote Method Invocation (RMI) requests that are received inbound.
By knowing the login configuration, you can plug in a custom login module that can handle specific cases for RMI logins.
Default | system.RMI_INBOUND |
This property defines the system JAAS login configuration that is used to perform application specific principal mapping.
Default | None |
This property, when set to true, enables the application specific principal mapping capability.
Default | false |
This property specifies the JAAS login configuration that is used for RMI requests that are sent outbound.
Primarily, this property prepares the propagated attributes in the Subject to be sent to the target server. However, you can plug in a custom login module to perform outbound mapping.
Default | system.RMI_OUTBOUND |
This property, when set to true, enables the original caller subject embedded in the WSSubjectWrapper object to be restored.
Default | false |
This property enables credentials that are authenticated in the current realm to be sent to any realm that is specified in the Trusted target realms field. The Trusted target realms field is available on the CSIv2 outbound authentication panel. This property enables those realms to perform inbound mapping of the data from the current realm.
Specifies that the user name credentials will always be filtered based on the User ID Map in the administrative console. This custom property assumes that you have an LDAP user registry.
When you log into the administrative console, the application server creates a user name that is stored in a credential. This user name is displayed and represents the user. The application server calls the getUserDisplayName() method to create the user name, and this API takes into account the User ID Map that is configured in the administrative console. The application server provides the User ID Map filter so you can customize the way user name is created.
If you have Trust Association Interceptor (TAI) configured, TAI creates the user name instead of the application server. When you create this custom property and set the value to true, TAI will also be able to use the User ID Map filter that is configured in the application server.
Default | false |
Specifies whether an 8-character limit for the user ID or password information is enforced when a local OS user registry is configured.
When this property is set to true, an 8-character limit for the user ID or password information is enforced when a local OS user registry is configured. If the user name or password that is specified during login contains more than eight characters, the login fails.
Default | false |
Determines whether System Authorization Facility (SAF) delegation can be used independently of SAF authorization. When this property is set to true, SAF delegation can be used whenever the user registry is a Federated Repository user registry, and is configured with a SAF user registry bridge.
There is no default value for this property.
Specifies that Federal Information Processing Standard (FIPS) algorithms are used. The application server uses the IBMJCEFIPS cryptographic provider instead of the IBMJCE cryptographic provider.
Default | false |
Use this property to specify whether the Certificate Expiration Monitoring tool should send configured notifications when there are no certificates that are about to expire or within the Expiration notification threshold. Setting this property to true prevents the Certificate Expiration Monitoring tool from sending configured notifications when there are no certificates that are about to expire or within the Expiration notification threshold.
The default value for this property is false
This security property is used to customize the "from address" of certificate expiration notification e-mail.
The value you assigned to this property should be an internet address, for example "Notification@abc-company.com" If this property is not set, WebSphere uses its e-mail fromAddress: "WebSphereNotification@ibm.com" .
Default | None |
This security property is used to customize the text encoding character set for certificate expiration notification e-mail.
WebSphere Application Server sends notification e-mail for certificate expiration in either US-English or the machine default character set (if non-English locale is specified). If you want a different text encoding character set for the certificate expiration notification e-mail, you can use this property to customize the text encoding character set.
Default | None |
Use this property to indicate whether a cookie with the value WASReqURL is honored when the custom form login processor is used.
When this property is set to true, the value of WASReqURL takes precedence over the current URL, and the WASReqURL cookie is removed from subsequent requests.
When this property is set to false, the value of the current URL takes precedence, and the WASReqURL cookie is not removed from subsequent requests.
Default | false |
This property is used by the auditing service that was introduced as a technical preview in Version 6. The auditing functionality is not available. Do not modify this property.
Default | J2EE=com.ibm.ws.security.audit.defaultAuditEventFactoryImpl |
This property is used to improve the response time for large topology configurations.
When this property is set to true the status of the of the SSL port endpoints does not display on the Manage endpoint security configurations page in the administrative console. Displaying the status of the SSL port endpoints sometimes makes the administrative console seem like it is no longer functioning because of a longer than expected response time.
Default | false |
This property enables decoding of the DNQUALIFIER attribute in the X.500 distinguished name when set to true and only provides decoding of the standard X.500 distinguished name (as defined by RFC 2253) when set to false. Restart the server after you change this value.
Default | false |
Default invocation order of Trust Association Interceptors (TAIs) in relation to Single Sign On (SSO) user authentication can be changed using this property. The default order is to invoke Trust Association Interceptors after SSO. This property is used to change the default order of TAI invocation with SSO. The property value is a comma (,) separated list of TAI class names to be invoked before SSO.
Default | none |
Type | string |
This property specifies whether (true) or not (false) the WebSphere Application Server uses the canonical form of the URL/HTTP host name in authenticating a client.
CWSPN0011E: An invalid SPNEGO token has been encountered while authenticating a HttpServletRequestYou can avoid an error message by setting this property to “true” and allowing WebSphere Application Server to authenticate using the canonical form of the URL/HTTP host name.
Default | false |
The com.ibm.websphere.security.ldap.groupDnSearchFilter property is used to overwrite the distinguished name group search filter. The value of the property should be the search filter, for example: (objectClass=group)
Default | none |
Type | string |
This custom property enables you to change the name of the realm that is placed in the token.
This custom property enables you to configure each cell to have its own LDAP host for interoperability and backward compatibility. Also, it provides flexibility for adding or removing the LDAP host dynamically. If you are migrating a previous installation, this modified realm name does not take effect until administrative security is re-enabled. To be compatible with a previous release that does not support the logic realm, the name must be the same name that is used by the previous installation. You must use the LDAP host name, including a trailing colon and port number.
Type | String |
The com.ibm.websphere.security.ldap.userDnSearchFilter property is used to overwrite the distinguished name user search filter. The value of the property should be the search filter, for example: (objectClass=user)
Default | none |
Type | string |
Specifies whether credential expiration check occurs for a local EJB call. Typically, when an EJB invokes another EJB that is located in a local machine, a direct method invocation occurs even if the credentials of the original invoker expire before the local EJB call occurs.
If this property is set to true, a credential expiration check occurs on a local EJB call before the EJB is invoked on the local machine. If the credentials have expired, the EJB call is rejected.
If this property is set to false, a credential expiration check does not occur for a local EJB call.
Default | false |
This property sets a size limit for WASPostParam cookies being generated by the security code.
Default | none |
This custom property specifies whether to limit the size of the CSIv2 session cache.
When you set this custom property value to true, you must set values for the com.ibm.websphere.security.util.csiv2SessionCacheIdleTime and com.ibm.websphere.security.util.csiv2SessionCacheMaxSize custom properties. When you set this custom property to false, the CSIv2 session cache is not limited. The default property value is false.
This property specifies the maximum size of the session cache after which expired sessions are deleted from the cache. Expired sessions are defined as sessions that are idle longer than the time that is specified by the com.ibm.websphere.security.util.csiv2SessionCacheIdleTime custom property.
Consider increasing the value of this custom property if a small cache size causes the garbage collection to run so frequently that it impacts the performance of the application server.
The range of values for this custom property is 100 to 1000 entries. By default, a value is not set.
This custom property only applies if you enable stateful sessions, enable the com.ibm.websphere.security.util.csiv2SessionCacheLimitEnabled custom property, and set a value for the com.ibm.websphere.security.util.csiv2SessionCacheIdleTime custom property.
This property specifies the time in milliseconds that a CSIv2 session can remain idle before being deleted. The session is deleted if the com.ibm.websphere.security.util.csiv2SessionCacheLimitEnabled custom property is set to a true value and the maximum size of the CSIv2 session cache is exceeded.
With a small value for the com.ibm.websphere.security.util.csiv2SessionCacheIdleTime custom property, the application server can clean out rejected sessions more frequently and potentially reduce resource shortages.
The range of values for this custom property is 60,000 to 86,400,000 milliseconds. By default, a value is not set.
This custom property only applies if you enable stateful sessions, enable the com.ibm.websphere.security.util.csiv2SessionCacheLimitEnabled custom property, and set a value for the com.ibm.websphere.security.util.csiv2SessionCacheMaxSize custom property
This custom property enables you to set the HTTPOnly attribute for single sign-on (SSO) cookies.
You can use the com.ibm.ws.security.addHttpOnlyAttributeToCookies custom property to protect cookies that contain sensitive values. When you set this custom property value to true, the application server sets the secure and HTTPOnly attribute for SSO cookies whose values are set by the server. Also, a true value enables the application server to properly recognize, accept, and process inbound cookies with HTTPOnly attributes and inhibit any cross-site scripting from accessing sensitive cookie information.
A common security problem, which impacts Web servers, is cross-site scripting. Cross-site scripting is a server-side vulnerability that is often created when user input is rendered as HTML. Cross-site scripting attacks can expose sensitive information about the users of the Web site. Most modern Web browsers honor the HTTPOnly attribute to prevent this attack. A cookie with this attribute is called an HTTPOnly cookie. Information that exists in an HTTPOnly cookie is less likely to be disclosed to a hacker or a malicious Web site. For more information about the HTTPOnly attribute, see the Open Web Application Security Project (OWASP) Web site.
Default | false |
In this release, the actual LTPA token data is not available from a WSCredential.getCredentialToken() call when called from an asynchronous bean. For an existing configuration, you can add the com.ibm.ws.security.createTokenSubjectForAsynchLogin custom property with a true value to allow the LTPAToken to be forwarded to asynchronous beans. This property allows portlets to successfully perform LTPA token forwarding. Make sure that you enter this custom property name as indicated because it is case sensitive. You must restart your application server after you enable this custom property.
Default | not applicable |
This property is the JAAS login configuration that is used for logins that do not fall under the WEB_INBOUND, RMI_OUTBOUND, or RMI_INBOUND login configuration categories.
Internal authentication and protocols that do not have specific JAAS plug points call the system login configuration that is referenced by com.ibm.ws.security.defaultLoginConfig configuration.
Default | system.DEFAULT |
Use the com.ibm.ws.security.failSSODuringCushion custom property to update custom JAAS Subject data for the LTPA token.
When you do not set this custom property to true, new JAAS Subjects might not contain the custom JAAS Subject data.
When this custom property is set to true, new JAAS Subjects might not contain the custom JAAS Subject data.
The default value is false.
Starting with Version 6.1.0.35, the default value for this property is true.
Use the com.ibm.ws.security.ltpa.forceSoftwareJCEProviderForLTPA custom property to correct an "invalid library name" error when you attempt to use a PKCS11 type keystore with a Java client.
Also, use this custom property if you are using
the IBMJCECCA provider because distributed and z/OS operating systems
use different provider types for hardware cryptography.
The ssl.client.props file points to a configuration file, which in turn, points to the library name for the cryptographic device. The code for the Java client looks for a keystore type for the correct provider name. Without this custom property, the keystore type constant for PKCS11 is not specified correctly as it references the IBMPKCS11Impl provider instead. Also, the Lightweight Third Party Authentication (LTPA) code uses the provider list to determine the Java Cryptography Extension (JCE) provider. This approach causes a problem when Secure Sockets Layer (SSL) acceleration is attempted because the IBMPKCS11Impl provider needs to be listed before the IBMJCE provider within the java.security file.
This custom property corrects both issues so that SSL and other cryptographic mechanisms can use hardware acceleration.
Set this custom property to true when you want to use a PKCS11 type keystore with a Java client.
Default | false |
Use this property to improve the CPU utilization during the sign() operation that occurs when a new LTPA2 (SSO) token is created. When this property is set to true, the product implements the Chinese Remainder Theorem (CRT) algorithm when signing the new token. This property has no effect on the old style LTPA token.
Default | false |
Specifies the actual host name to which the application server can resolve an alias host name for SPNEGO single sign-on. You can then dynamically add or modify an alias name in the DNS without changing the application server's configuration.
For more information on how to use this custom property, read the topic on using an alias host name for SPNEGO TAI authentication.
Specifies the application server to use Canonical support.
For more information on how to use this custom property, read the topic on using an alias host name for SPNEGO TAI authentication.
This property determines whether to send LtpaToken2 and LtpaToken cookies in the response to a Web request (interoperable).
When this property value is false, the application server just sends the new LtpaToken2 cookie which is stronger, but not interoperable with some other products and Application Server releases prior to Version 5.1.1. In most cases, the old LtpaToken cookie is not needed and you can set this property to false.
Default | true |
This is a custom property of user registries. This property alters the behavior of creating WSCredential.
A setting of false indicates that the security name returned by a user registry is always used to construct WSCredential.
A setting oftrue indicates that either a security name that is supplied by login module is used or a display name that was supplied by a user registry is used. This setting is compatible with WebSphere Application Server version 6.0.2 and older releases.
Default | false |
Specifies the method names on the UserRegistry interface, such as getRealm, getUsers, and isValidUser, that you do not want protected from remote access. If you specify multiple method names, separate the names with either a space, a comma, a semi-colon, and a separator bar. See your implementation of the UserRegistry interface file for a complete list of valid method names.
If you specify an * as the value for this property, all methods are unprotected from remote access.
If a value is not specified for this property, all methods are protected from remote access.
If an attempt is made to remotely access a protected UserRegistry interface method, the remote process receives a CORBA NO_PERMISSION exception with minor code 49421098.
There is no default value for this property.
This property determines the behavior of a single sign-on LtpaToken2 login.
When this property value is set to true, the token contains a custom cache key, and the custom Subject cannot be found, the token is used to log in directly as the custom information needs to be gathered again. A challenge occurs so that the user to login again. When this property value is set to false and the custom Subject is not found, the LtpaToken2 is used to login and gather all of the registry attributes. However, the token might not obtain any of the special attributes that downstream applications might expect.
Default | true |
This property is the JAAS login configuration that is used for Web requests that are received inbound.
By knowing the login configuration, you can plug in a custom login module that can handle specific cases for Web logins.
Default | system.WEB_INBOUND |
This property is used to enable a server to use the user identity for the z/OS started task as the server identity when calling transactional methods.
This property is used to enable a server to use the user identity for the z/OS started task as the server identity when calling transactional methods, such as commit(), and prepare(), that require the server identity. This behavior occurs regardless of the server identity setting for that server.
As an example, a server can be configured to use the automatically generated server identity, which is not the actual identity stored in a user repository. Furthermore, this server might need to communicate with CICS 3.2, and CICS 3.2 requires the use of System Authorization Facility (SAF) identities. If com.ibm.ws.security.zOS.useSAFidForTransaction is set to true, then the server uses a System Authorization Facility (SAF) identity to communicate with CICS instead of using the automatically generated identity.
Default | false |
This property determines whether a received LtpaToken2 cookie should search for the propagated attributes locally before searching the original login server that is specified in the token. After the propagated attributes are received, the Subject is regenerated and the custom attributes are preserved.
You can configure the data replication service (DRS) to send the propagated attributes to front-end servers such that a local dynacache lookup can find the propagated attributes. Otherwise, an MBean request is sent to the original login server to retrieve these attributes.
Default | true |
This property is used by the auditing service that was introduced as a technical preview in Version 6. The auditing functionality is not available. Do not modify this property.
Default | DEFAULT = com.ibm.ws.security.audit.defaultAuditServiceProviderImpl |
This property specifies the Lightweight Third Party Authentication (LTPA) token factories that can be used to validate the LTPA tokens.
Validation occurs in the order in which the token factories are specified because LTPA tokens do not have object identifiers (OIDs) that specify the token type. The Application Server validates the tokens using each token factory until validation is successful. The order that is specified for this property is the most likely order of the received tokens. Specify multiple token factories by separating them with a pipe (|) without spaces before or following the pipe.
Default | com.ibm.ws.security.ltpa.LTPATokenFactory | com.ibm.ws.security.ltpa.LTPAToken2Factory | com.ibm.ws.security.ltpa.AuthzPropTokenFactory |
This property specifies the implementation that is used for an authentication token in the attribute propagation framework. The property provides an old LTPA token implementation for use as the authentication token.
Default | com.ibm.ws.security.ltpa.LTPATokenFactory |
This property specifies the implementation that is used for an authorization token. This token factory encodes the authorization information.
Default | com.ibm.ws.security.ltpa.AuthzPropTokenFactory |
This property specifies the implementation that is used for a propagation token. This token factory encodes the propagation token information.
The propagation token is on the thread of execution and is not associated with any specific user Subjects. The token follows the invocation downstream wherever the process leads.
Default | com.ibm.ws.security.ltpa.AuthzPropTokenFactory |
This property specifies the implementation that is used for a Single Sign-on (SSO) token. This implementation is the cookie that is set when propagation is enabled regardless of the state of the com.ibm.ws.security.ssoInteropModeEnabled property.
By default, this implementation is the LtpaToken2 cookie.
Default | com.ibm.ws.security.ltpa.LTPAToken2Factory |
The IbmPKIX trust manager is enabled in WebSphere® Application Server by default. The IbmPKIX trust manager allows certificate revocation checking to occur. The following customer properties are available to be used with the IbmPKIX trust manager:
This property configures revocation checking for the Java™ Virtual Machine (JVM). This property is set to false by default because the default WebSphere certificates used for SSL communication do not contain certificate revocation list (CRL) distribution points or Online Certificate Status Protocol (OCSP) information. The default value is false.
For certificates that do not contain an internal CRL distribution point, the following properties can used so the revocation status will be checked against a remote LDAP server containing the CRL.
The default value is none.
This property specifies the LDAP server port. A port value of 389 will be used by default if no LDAP server port is specified. The default value is 389.
Use this custom property to permit custom HTTP methods
The security constraints for a Web module must specify standard HTTP methods and the custom property cannot be one of the HTTP methods in the security constraints.
This property is no longer used. Instead, use WEB_INBOUND login configuration.
Default | true |
The NullDynamicPolicy.getPermissions method provides an option to delegate a default policy class to construct a Permissions object when this custom security is set to true. When the security.useDefaultPolicyWhenJ2SDisabled custom property is set to false, an empty Permissions object is returned.
Default | false |
This property is used to indicate whether BBO.TRUSTEDAPPS checks are enforced. When this property is set to true, BBO.TRUSTEDAPPS checks are enforced. This means that any user who does not have READ access to this SAF profile is not allowed to log into the administrative console.