true
= Automatic certificate discovery is enabled, without user intervention required.
false
= Automatic certificate discovery is disabled. When the Policy Manager attempts to trust a server certificate for the first time, a confirmation dialog is displayed and you must explicitly accept or reject the certificate.

true
= mapping information is saved in the
API Gateway
audit, enabling them to be viewed in the Gateway Audit Events window.
false
= mapping information is not saved in the
API Gateway
audit.

true
= mapping information is saved with the service metrics, allowing them to be used in the Dashboard.
false
= mapping information is not saved with the service metrics.

W3C ISO 8601 (http://www.w3.org/TR/NOTE-datetime)
HTTP-Date (RFC1123, RFC 850, asc time)
RFC 1123  Example: Sun, 06 Nov 1994 08:49:37 GMT
RFC 822 (and RFC1036) Example: Sun, 06 Nov 94 08:49:37 GMT
RFC 850 Example: Friday, 19-Nov-82 16:14:55 EST
asc time Example:. Fri Nov 12 13:02:02 2012

The string must be formatted as <format><^pattern$>.
The pattern must begin with the ^ character and end with the $ character.
White space is not required and is ignored if present.
Any pairs with an invalid format or pattern are ignored and an audit is generated.
The Policy Manager does not validate the value for this property.

yyyy-MM-dd'T'HH:mm:ss.SSSXXX ^\d{4}-\d{2}-\d{2}T\d{2}:
\d{2}:\d{2}\.\d{3}(?:Z|(?:\+|-)\d{2}:\d{2})$
yyyy-MM-dd'T'HH:mm:ss.SSXXX ^\d{4}-\d{2}-\d{2}T\d{2}:
\d{2}:\d{2}\.\d{2}(?:Z|(?:\+|-)\d{2}:\d{2})$
yyyy-MM-dd'T'HH:mm:ss.SXXX ^\d{4}-\d{2}-\d{2}T\d{2}:
\d{2}:\d{2}\.\d{1}(?:Z|(?:\+|-)\d{2}:\d{2})$
yyyy-MM-dd'T'HH:mm:ssXXX ^\d{4}-\d{2}-\d{2}T\d{2}:
\d{2}:\d{2}(?:Z|(?:\+|-)\d{2}:\d{2})$
yyyy-MM-dd'T'HH:mmXXX ^\d{4}-\d{2}-\d{2}T\d{2}:
\d{2}(?:Z|(?:\+|-)\d{2}:\d{2})$
yyyy-MM-dd ^\d{4}-\d{2}-\d{2}$
yyyy-MM ^\d{4}-\d{2}$
yyyy ^\d{4}$
EEE, dd MMM yyyy HH:mm:ss z ^[a-zA-Z]{3},\s\d{2}
\s[a-zA-Z]{3}\s\d{4}\s\d{2}:\d{2}:\d{2}\s(?:
[a-zA-Z]{3}|(?:\+|-)\d{4})$
EEE, dd MMM yy HH:mm:ss Z ^[a-zA-Z]{3},\s\d{2}
\s[a-zA-Z]{3}\s\d{2}\s\d{2}:\d{2}:\d{2}\s(?:
[a-zA-Z]{3}|(?:\+|-)\d{4})$
EEE, dd-MMM-yy HH:mm:ss z ^
(?:Monday|Tuesday|Wednesday|Thursday|Friday|Saturday|Sunday),
\s\d{2}-[a-zA-Z]{3}-\d{2}\s\d{2}:\d{2}:\d{2}\s(?:[a-zA-Z]{3}|(?:\+|-)\d{4})$
EEE MMM dd HH:mm:ss yyyy ^[a-zA-Z]{3}\s[a-zA-Z]{3}
\s(\d{2}|\s\d)\s\d{2}:\d{2}:\d{2}\s\d{4}$

true
= If an assertion refers to a private key in a non-existent keystore, the
API Gateway
will check all other keystores for an identical private key alias. If one is found, it will be used instead. In the Policy Manager, a warning validator message is displayed for any affected assertions.
false
=  If an assertion refers to a private key in a non-existent keystore, an error is returned and the policy containing this assertion will be inoperative. Other keystores are not examined.

true
= MTOM-encoded messages containing a WS-Security header that is processed by the
API Gateway
is automatically decoded to a regular SOAP message for security processing.
false
= MTOM-encoded messages is not automatically decoded prior to WS-Security processing. An undecoded secure MTOM message can cause WS-Security processing to fail.

OFF
: No response to any ping attempts.
REQUIRE_CREDS
: Responds only when request is submitted using SSL on port 8443, with credentials in the request.
OPEN
: Minimal response when request is submitted without SSL (port 8080); full response when request is submitted with SSL (port 8443).
MONITOR
: Returns a minimal status message to the client, while denying access to any node system information.

true
= compressed requests are accepted by the
API Gateway
false
= all compressed requests are rejected

true
= compressed response can be returned to the client
false
= force a non-compressed response from the
API Gateway
to the client, regardless of the accept-encoding requested response

Your
API Gateway
repeatedly validates the same signed XML snippets (for example, SAML assertions) and maximum throughput is important.
Your organization's security policy permits cached signatures.
Caching code in the signature validation code path is acceptable. 

t
rue
= Places the RSA software cryptographic provider into FIPS mode, but security providers from the runtime environment continue to be available. If a
API Gateway
feature is enabled that requires a non-FIPS algorithm (for example, the Certificate Discovery Service or an SSL cipher that uses RC4 or MD5), then the
API Gateway
tries to use the built-in security provider for that feature.

false
= The built-in non-FIPS Sun provider is always used; FIPS mode is never enabled.

If the
API Gateway
- XML VPN Client is used, do not remove the "secure_span" actor or role.
Any new actor or role added to these properties are treated in the same manner as the "secure_span" actor when it comes to processing of security headers in routing assertions (that is, if the "Remove Layer 7 actor and mustUnderstand attributes from processed Security header" option is chosen for WSS header handling in a routing assertion property).

true
=  Messages containing "mustUnderstand" SOAP headers other than "Security" and "Timestamp" that are addressed to the
API Gateway
role are rejected immediately, during security processing.
false
= Messages containing such SOAP headers are passed through security processing and into policy processing.

true
– Forces the use of the XSLT 2.0 engine to process v1.0 stylesheets in software.
false
– Uses the XSLT 2.0 engine only for v2.0 XSLT/XPath operations. This setting is the default.