You are viewing the documentation for Blueriq 16. Documentation for other versions is available in our documentation directory.
Legacy properties are properties to configure legacy behavior in specific cases. This legacy behavior is deprecated and should therefore not be used, as it will be removed in a future release. The properties exist to help during a transitioning period towards the new behavior.
| Subject | Property | Explanation | Default | Introduced in | Removed in | |
|---|---|---|---|---|---|---|
| Runtime | blueriq.legacy.legacy-rest-validation | With the introduction of reporting all errors during parsing of incoming JSON rest requests or responses, the error-message content changes. If this is not (yet) desirable the runtime reverts back to the previous implementation by setting the property to true | false | 15.12 | 17.0 | application.properties |
| Runtime | blueriq.legacy.legacy-rest-response-validation | Blueriq 15 started to also include field validations when parsing a REST response, which may result in the REST service client call failing for messages that used to be accepted in earlier versions. Setting this property to true reverts to the old behavior. | false | 16.11.4 | 18.0 |
|
| Runtime | blueriq.legacy.legacy-jwt-claims-path-expression | Setting this property to true enables the legacy, comma-separated expression format for JWT claim paths in JWT Mapping properties. The legacy format contains a comma-separated path to a claim in the JWT body. For example if the JWT body contains the following claims: {
... other claims ...
"realm_access": [
"roles": ["role1", "role2"]
]
... other claims ...
}
a value of "realm_access,roles" would indicate that the roles claim nested within the realm_access claim should be sourced. | false | 16.7 | 17.0 |
|
| Runtime | blueriq.legacy.mapping-to-same-module | If SOAP and REST clients/webservices specify a data mapping, a new profile is always created even if the webservice is defined in the entry-point module. The legacy mode reverts to the behavior where the mapping would be executed across the same profile, potentially resulting in unexpected behavior. | false | 16.8 | 17.0 |
|
Overview
Content Tools