1. RESTful Edit Management Interface for Oracle WebLogic Server
  2. Tasks
  3. Feature Compatibility

Modify This Feature Compatibility

post

/management/weblogic/{version}/edit/featureCompatibility

Modify this feature compatibility.

Request

Supported Media Types
Path Parameters
Header Parameters
  • The 'X-Requested-By' header is used to protect against Cross-Site Request Forgery (CSRF) attacks. The value is an arbitrary name such as 'MyClient'.
Body ()

Must contain the modified feature compatibility model.

Root Schema : Feature Compatibility
Type: object
Show Source
  • Default Value: true

    Returns whether reused cross-domain T3S connections require trust validation. When enabled, a reverse cross-domain lookup cannot reuse an established T3S connection and must pass a fresh SSL trust check. Changes take effect after the server is restarted.

  • Read Only: true
    Default Value: false

    Return whether the MBean was created dynamically or is persisted to config.xml

  • Read Only: true

    Return the unique id of this MBean instance

  • Default Value: true

    Controls strict validation of IIOP business interfaces used during client stub generation.

    When enabled, WebLogic Server rejects a business interface that is not recognized as a remote interface. When disabled, WebLogic Server permits a locally visible plain business interface for a legacy IIOP client only when the IOR has no codebase.

  • Default Value: true

    Controls strict validation of typed IIOP serialization wrappers. When enabled, incompatible wire classes, including serialization wrappers, are rejected before readResolve(). When disabled, legacy typed IIOP readResolve proxy behavior is preserved.

  • Default Value: true

    Returns whether IIOP request and reply service-context valuetypes are filtered by the unauthenticated deserialization allowlist.

    When enabled, WebLogic Server applies the unauthenticated deserialization filter while reading IIOP request and reply service contexts. The filter does not apply to application values in request or reply bodies. When disabled, WebLogic Server preserves legacy IIOP service-context unmarshalling behavior.

    A value of true enables the tightened filtering. A value of false preserves legacy behavior.

  • Default Value: true

    Specifies whether JAX-WS SEI endpoints reject requests whose SOAP operation does not resolve to an SEI method before invoking downstream tubes.

    When enabled, an unknown operation receives an Invalid operation SOAP fault before downstream processing, including WorkContext processing. When disabled, the request follows the legacy path, which invokes downstream tubes without method-level authorization for that operation. This protection is enabled by default. A change takes effect for subsequent requests without restarting the server.

  • Default Value: true

    Returns whether the JNDI additional factory allowlists are enabled.

    When enabled, WebLogic Server applies the SecurityConfigurationMBean.JNDIAdditionalInitialContextFactoriesAllowed and SecurityConfigurationMBean.JNDIAdditionalReferenceFactoriesAllowed allowlists before caller-supplied JNDI factories can be used. When disabled, WebLogic Server preserves legacy initial context factory and reference factory behavior.

  • Default Value: true

    Returns whether policy enforcement is enabled for authorization of JNDI namespace binding changes.

    When enabled, WebLogic Server applies tightened authorization and protocol checks before namespace write operations such as bind, rebind, unbind, rename, subcontext creation, sharable namespace mutation, or IIOP CosNaming mutation can change server-side JNDI bindings. When disabled, WebLogic Server preserves legacy remote JNDI mutation and protocol-specific mutation behavior.

    A value of true enables the tightened policy for this category. A value of false preserves legacy behavior.

  • Default Value: true

    Returns whether the JNDI outbound connection allowlist is enabled.

    When enabled, WebLogic Server applies the SecurityConfigurationMBean.JNDIOutboundConnectionsAllowed allowlist to JNDI provider URLs and URL-shaped lookup inputs. When disabled, WebLogic Server preserves legacy outbound JNDI connection behavior.

  • Read Only: true

    The user-specified name of this MBean instance.

    This name is included as one of the key properties in the MBean's javax.management.ObjectName

    Name=user-specified-name

    Constraints

    • legal null

  • Optional information that you can include to describe this configuration.

    WebLogic Server saves this note in the domain's configuration file (config.xml) as XML PCDATA. All left angle brackets (<) are converted to the xml entity <. Carriage returns/line feeds are preserved.

    Note: If you create or edit a note from the Administration Console, the Administration Console does not preserve carriage returns/line feeds.

  • Default Value: true

    Specifies whether SAML 2.0 artifact-resolution requesters must be authenticated before accessing the artifact cache.

    When enabled, WebLogic Server requires an enabled partner matching the request issuer, validates configured authentication and any supplied or required signature, and consumes the artifact only for an authenticated intended recipient. A verified signature or a partner-matched TLS client certificate is required; shared Basic authentication alone does not identify a partner.

    This protection is enabled by default. Configure request signing or partner-matched TLS client authentication at both partners. Set this attribute to false only when legacy interoperability is required; doing so permits artifact retrieval before authentication and disables this protection. Unsetting the attribute restores the enabled default. A change takes effect for subsequent requests without restarting the server.

  • Minimum Value: -1
    Default Value: 65535

    Specifies the maximum allowed size, in bytes, of a serialized SerializableWorkContext payload read from a WorkArea input stream.

    A value of -1 disables the compatibility limit and preserves legacy behavior. To enable the limit, set this attribute to a positive byte count. A value of zero leaves the byte limit unapplied but keeps the additional unauthenticated deserialization filter enabled. Raise the value only if legitimate WorkContext payloads require more space.

    When this MBean is available, its effective value, including the default, takes precedence over the legacy weblogic.workarea.serializableWorkContext.maxLength JVM property.

  • Default Value: true

    Controls whether Spring JtaTransactionManager skips resolving serialized JNDI names while deserializing.

    When enabled, transient JTA handles are not restored from serialized JNDI names. When disabled, WebLogic Server preserves the legacy Spring behavior of resolving serialized JNDI names during deserialization. WebLogic's configured JTA lookup during normal bean initialization is not affected.

  • Default Value: true

    Specifies whether T3 RJVM identify processing should enable replay protection for JVMIDs signed by legacy cross-domain credentials.

    Enabling this attribute prevents a replayable legacy cross-domain credential-signed JVMID from promoting a freshly identified inbound RJVM to trusted-server state. Set this attribute to false to preserve legacy global-domain-trust behavior.

  • Default Value: true

    Returns whether T3 server routing is limited to trusted servers.

    When enabled, WebLogic Server requires routed T3 destinations to be known or configured before forwarding traffic. When disabled, WebLogic Server preserves legacy T3 server routing compatibility for trusted server-to-server messages whose destination is supplied on the wire.

    A value of true enables the tightened routing checks. A value of false preserves the legacy routing behavior.

  • Items
    Title: Items

    Return all tags on this Configuration MBean

  • Read Only: true

    Returns the type of the MBean.

    Constraints

    • unharvestable
  • Default Value: true

    Controls whether WLDF script actions require the script path to resolve under DOMAIN_HOME/bin/scripts.

  • Default Value: true

    Returns whether WebLogic Server validates certificate chains supplied in the WL-Proxy-Client-Cert header before using them for X.509 identity assertion.

    When enabled, WebLogic Server validates the proxy-supplied certificate chain against the configured WebLogic Server client certificate trust anchors before setting the jakarta.servlet.request.X509Certificate request attribute. Invalid, untrusted, expired, malformed, or otherwise unverifiable certificates are rejected. When disabled, WebLogic Server preserves the legacy proxy client certificate behavior.

  • Default Value: true

    Returns whether tightened validation is enabled for WorkContext implementation classes read from WorkArea input streams.

    When enabled, WebLogic Server validates WorkContext class names and resolved classes before constructing WorkContext implementations on T3, JMS, IIOP, legacy XML SOAP, and other WorkArea readers that apply this attribute. The tightened policy on those readers limits unauthenticated or untrusted inbound input to WebLogic built-in and product WorkContext implementations. Protocol compatibility paths can preserve SerializableWorkContext behavior, but authentication alone does not permit arbitrary custom WorkContext implementations when this attribute is enabled.

    Legacy XML WorkArea SOAP, when explicitly enabled with weblogic.wsee.workarea.workContext.oldFormat.support, applies these class checks before class initialization, construction, and readContext. The format opt-in is independent: this attribute does not enable that format. Disabling this attribute preserves legacy XML class admission; existing XML structural checks remain in effect.

    Custom WorkContexts created by server application code can propagate through collocated RMI calls between applications. WorkContexts admitted by the applicable WorkArea input factories, including XML and binary SOAP, retain their received origin. Subsequent collocated copies apply inbound validation under the effective policy, including to contexts received while this attribute was disabled. Deferred received SerializableWorkContext payloads retain their separate payload validation.

    A value of true enables the tightened WorkContext class checks. A value of false preserves legacy behavior for patch compatibility.

  • Minimum Value: -1
    Default Value: 65535

    Specifies the maximum allowed size, in bytes, of an ASCII field read from the WorkArea binary encoding in which the field length is represented by a four-byte signed integer. This limit does not apply to transport-specific WorkContext encodings, including T3 and IIOP, which use separate decoding paths and are not governed by this attribute.

    A value of -1 leaves the cap unapplied and preserves legacy behavior. Every value greater than or equal to 0 is a literal byte cap; 0 has no special meaning and permits only zero-length ASCII fields. Raise the value only if legitimate WorkContext fields require more space.

  • Default Value: true

    Specifies whether WS-AT replay completion requests with no matching local transaction should be ignored instead of rolling back a recovery resource created from the caller-supplied ReplyTo endpoint.

    Enabling this attribute selects the hardened unknown-transaction replay completion behavior. Set this attribute to false to preserve legacy behavior.

  • Default Value: true

    Controls whether WS-AT registration requires proof that the caller received the exported coordination context before participant enlistment.

    Enabling this attribute emits a per-transaction registration secret in WLS-generated coordination contexts and requires unauthenticated registration requests to echo the matching secret before enlistment. Set this attribute to false to preserve legacy WS-AT interoperability.

Nested Schema : Items
Type: array
Title: Items

Return all tags on this Configuration MBean

Show Source
Security
  • Type: basic
    Description: A user in the Admin security role.
Back to Top

Response

200 Response

Back to Top