Changelog

[SWIFT Microgateway BCI 1.0.5.8] - 2022-04-19

Added

• Support for configurable API calls timeout
  configuration:
  environment: TEST
  swift_microgateway:
       port: 9007
       call_timeout_sec: 120
       ssl:
          key_store_type: JKS

[SWIFT Microgateway 2.0.6] - 2022-03-15

Added

• Automatically identifying the version of SWIFT Microgateway running in the field
• Automatically identifyig the version of SWIFT Security SDK, SWIFT Microgateway is based upon, running in the field

Patching

• Please note, the patching procedure documented in the Getting Started Guide (chapter "Applying SWIFT Microgateway Patch Releases") cannot be applied for going from SWIFT Microgateway 1.0.6.x to SWIFT Microgateway 2.0.2

Migration

• You cannot migrate from SWIFT Microgagateway 1.0.6.x to SWIFT Microgateway 2.0.2 automatically. You will have to install and configure SWIFT Microgateway 2.0.6 from scratch using either SWIFT Microgateway Microservices, curl script calling SWIFT Microgateway Microservices or SWIFT Microgateway Front-End 2.0.2

[SWIFT Microgateway 1.0.6.17] - 2022-03-15

Added

• Support for configurable API calls timeout
  configuration:
  environment: TEST
  swift_microgateway:
       port: 9007
       call_timeout_sec: 120
       ssl:
          key_store_type: JKS
• Automatically identifying the version of SWIFT Microgateway running in the field
• Automatically identifying the version of SWIFT Security SDK, SWIFT Microigateway is based upon, running in the field

Changed

• Fix performance issue observed when an instance of SWIFT Microgateway is called by more than 50 threads simultaneosuly
• Improving error reporting when Update Payment Status GPI API calls are failing

Removed

• Unused log4j libraries from SWIFT Microgateay Configuration Utility

Patching

• Customers of prior SWIFT Microgateway version 1.0.6.16 should follow the procedure outlined in the Getting Started Guide, chapter "Applying SWIFT Microgateway Patch Releases"
• Do the whole backup of your SWIFT Microgateway 1.0.6.8 installation that you use in T&T (everything which goes under the root folder of SWIFT Microgateway 1.0.6.8 installation)
• Stop the existing SWIFT Microgateway 1.0.6.8 instance in T&T if it is running
• In the existing installation change lib/swift-mgw-1.0.6.8.jar for lib/swift-mgw-1.0.6.16.jar (the previous swift-mgw-1.0.6.8.jar must be deleted)
• In the existing installation change lib/internal/swift-security-sdk-2.0.6.jar for lib/internal/swift-security-sdk-2.0.11.jar (the previous swift-security-sdk-2.0.6.jar must be deleted)
• Change the reference for swift-security-sdk-2.0.6.jar in the bin/start.bat for swift-security-sdk-2.0.11.jar if you use Windows
• Restart the existing instance of SWIFT Microgateway which will be started now as SWIFT Microgateway 1.0.6.16
• Redo your API tests

[SWIFT Microgateway 2.0.2] - 2021-12-09

Added

• Positioning the software for processing inbound API calls
• Validating outbound API calls according OpenAPI specifications based on ISO 20022 data components
• Validating inbound API calls according to OpenAPI specifications based on ISO 20022 data components
• Supporting Open and Automatic SAG switch-over architectures
• Providing solution for running SWIFT Microgateway nodes in a cluster
• Providing Business Continuity and Business Consistency through the use of In-Memory Data Grid technology
• Providing a single interface to a back-office for interfacing with a cluster as a whole
• Positioning SWIFT SDK on top of the cluster for resolving load balancing and fault-tolerance automatically
• Extending SWIFT APIs reach toward Message-oriented middleware (MOM) customers base – providing productized AMQP Connector for making and receiving API calls
• Providing Local KMS for storing software certificates and shared secrets in AES encrypted form accessed via secure local API
• Providing Reference Implementation based on SWIFT SDK for integrating inbound API calls with Core Banking Systems
• Ability to enable/disable Configuration, Management and Monitoring Microservices
• Microservice for validating the software and configuration data integrity
• Providing configurable HTTP timeouts for connecting, calling, writing, and reading
• Providing X-SWIFT-Signature in API response to a back-office application in the form of a signed JWT (software and hardware certificate based) so it can be stored in an archive managed by a customer
• New SWIFT Microgateway Front-End 2.0.2 for configuring SWIFT Microgateway 2.0.2
• SWIFT Microgateway Front-End 2.0.2 not being dependent Java

Changed

• Fix performance issue observed when used from more than 10 business applications at the same time. This fix has been applied since the version 1.0.6.7

Security

• Anonymizing security artefacts (consumerSecret, sharedSecret) returned by Configuration Microservice
• Password protected command line utility used for decrypting the YAML bootstrap configuration file

Patching

• Please note, the patching procedure documented in the Getting Started Guide (chapter "Applying SWIFT Microgateway Patch Releases") cannot be applied for going from SWIFT Microgateway 1.0.6.x to SWIFT Microgateway 2.0.2

Migration

• You cannot migrate from SWIFT Microgagateway 1.0.6.x to SWIFT Microgateway 2.0.2 automatically. You will have to install and configure SWIFT Microgateway 2.0.2 from scratch using either SWIFT Microgateway Microservices, curl script calling SWIFT Microgateway Microservices or SWIFT Microgateway Front-End 2.0.2

[SWIFT Microgateway 1.0.6.8] - 2021-09-20

Added

• Support for GPI API v5

Changed

• Fix performance issue observed when used from more than 10 business applications at the same time. This fix has been applied since the version 1.0.6.7

Patching

• Customers of prior SWIFT Microgateway version 1.0.6.x should follow the procedure outlined in the Getting Started Guide, chapter "Applying SWIFT Microgateway Patch Releases"

[SWIFT Microgateway BCI 1.0.5.6] - 2021-08-31

Added

• Support for g4C API v4

Changed

• Fix performance issue observed when used from more than 10 business applications at the same time

Patching procedure

• Customers of prior SWIFT Microgateway BCI version 1.0.5.x should follow the procedure outlined in the Getting Started Guide, chapter "Applying SWIFT Microgateway Patch Releases"