Traffic Parrot 5.46.7 released, what's new?

We have just released version 5.46.7. Here is a list of the changes that came with the release:

Features

• Added support for sending one or more JMS text messages after an HTTP or gRPC response, configured via mapping JSON:

  "postServeActions" : [ {
      "name" : "send-jms-message",
      "parameters" : {
        "jmsConnectionId" : "(connection id from jms-connections.json)",
        "destination" : {
          "name" : "queue-name",
          "type" : "QUEUE"
        },
        "variables" : {
          "id" : "{{randomValue length=24 type='ALPHANUMERIC'}}"
        },
        "properties" : {
          "id" : "{{variables.id}}"
        },
        "jsonBody" : {
          "id" : "{{variables.id}}",
          "fieldFromRequest" : "{{originalRequest.jsonBody.requestField}}",
          "fieldFromResponse" : "{{originalResponse.jsonBody.responseField}}"
        },
        "delayDistribution" : {
          "type" : "fixed",
          "milliseconds" : 500
        }
      }
  } ]

• Added additional Okta JWT access token verification
• Added gRPC native transport for Apple ARM based processors

Fixes

• Fixed desktop issue where the start and stop scripts would steal focus on launch
• Fixed logging issue where HTTP and HTTPS GUI ports would be printed in the logs even if a port is disabled
• Fixed a DNS resolution failure issue on Mac
• Improved OpenAPI parser compatibility
• Improved error message when script runtime is missing

Changes

• Upgraded bundled JRE from 8u392 to 8u402
• Upgraded gRPC from 1.60.0 to 1.63.0
• This release is compatible with the MQ com.ibm.mq.allclient JAR up to version 9.3.4.1
• When using IBM MQ Advanced for Developers Docker icr.io/ibm-messaging/mq:9.3.4.0-r1 and above, MQ_APP_PASSWORD must be set for the app user, the default lack of password is no longer supported by the container
• IBM MQ username and password are now interpreted as null if set to "" or "null" in the connection JSON configuration
  • To configure a "" value use "<empty>"
  • To configure a "null" value use "<null>"
• Improved JMS message logging for null property values
• Library upgrades to fix OWASP issues