1. Home
  2. Swift Microgateway Changelog

Swift Microgateway Changelog

Changelog

All notable changes to this project will be documented on this page.

[Swift-Microgateway-2.17.2] - 2023-09-01

Security

  • Upgrades to frameworks and third-party software to reduce the potential vulnerabilities reported by security tools and software scanners.

Patching

  • Unpackage the Swift Microgateway package to a new directory. Migrate the contents of the “db” folder and “config” folder to the new installation.

[Swift-Microgateway Front End -2.0.4] - 2023-09-01

Added

  • Minor usability improvement when creating security profiles.

Migration

  • Previous versions of Swift Microgateway Front-End can be un-installed. Unpackage the downloaded software to a new folder and start the Swift Microgateway Front-End with the shortcut provided.

[SWIFT Microgateway 2.17.1-4] - 2023-08-08

Fixed

  • Included Swift Microgateway examples on how to use Microservices in the Postman collection.

[SWIFT Microgateway 2.0.16] - 2023-08-08

Fixed

  • Included Swift Microgateway examples on how to use Microservices in the Postman collection.

[Swift-Microgateway BaaS-2.17.1] - 2023-07-17

Added

Swift Microgateway BaaS (Backend-as-a-Service) includes the following enhancements:

  • Provides a reference on how to Pre-validate Beneficiary Account for Data Providers.
  • Local encrypted data storage of account data for names matching and support for external storage.
  • Includes Swift Names Matching SDK supporting several industry standard names matching algorithms.
  • Configurable parameters to customize exact and close names matching results.

Fixed

  • Swift Microgateway BaaS is built upon the current Swift Microgateway Release 2.17.1.
  • There are no additional changes or fixes; only functional enhancements mentioned above have been added.

Patching and Migration

  • This is a first release of Microgateway BaaS and requires a new instance of the Microgateway. Current Microgateway configuration can be cloned into the new instance.

[Swift-Microgateway-2.17.1] - 2023-06-23

Added

  • Ability to add new APIs to the existing Postman Collection of Swift Microgateway (code re-generation)
  • Supportinfo scripts to gather configuration information from the H2 database (1 way TLS only)
  • Software integrity checks on start-up of Swift Microgateway
  • Sample script for command line configuration of Swift Microgateway
  • Swift Microgateway logging in Common Event Format. Please use setting below under mgw config
    logging: cef-format-enabled: true

Fixed

  • Instant Cash Reporting (ICR) - Account path parameter support for slashes '/'
  • Warning when pilot calls are made in Live and vice versa
  • Improved loading of Local OAS Specifications

Security

  • Remove information exposure about of third party COTS/libs versions in request and responses

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.17.0-11. The same is applicable for SWIFT Microgateway 2.x to SWIFT Microgateway 2.17.0-11

Migration

  • See Migration section of release Swift Microgateway 2.17.0-7

[Swift Microgateway Frontend-2.0.3] 2023-06-20

Added

  • Ability to import certificates from either JKS (Java 8) & PKCS12 (Java 17) keystores

Fixed

  • SAG profile types are correctly displayed as SAG (HSM) of Soft (certificate based) after creation

Patching

  • Swift Microgateway Frontend packages are self extracting windows installable programs. Previous versions of Swift Microgateway Frontend can be un-installed, and a new version installed. Several versions of Swift Microgateway Frontend can also be installed on the same host.

[SWIFT Microgateway 2.17.0-7] - 2023-03-03

Added

  • Ability to disable interactions with Central API Repository
  • Ability to dynamically change log levels in log files via Swift Microgateway Management Microservice
  • Supporting connectivity with Swift API Sandbox available on Internet
  • Ability to purge API contracts from Configuration Management database imported via Local and/or Central API Repositories. This feature can be used to refresh API contracts from Local/Central API Repositories using Swift Microgateway Management Microservice
  • Updated Postman Collection triggering the above action

Fixed

  • Fixing the logic of API session establishment process in case multiple Business Application profiles are used

Security

  • Providing an ability to communicate with Swift API Platform via HTTP Forward Proxy not mandating a password to be specified - built-in HTTP Forward Proxy available with Alliance Web Platfrom

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.17.0-1

Migration

  • You cannot migrate from SWIFT Microgagateway 1.0.6.x to SWIFT Microgateway 2.17.0-7 automatically. You will have to install and configure SWIFT Microgateway 2.17.0-7 from scratch using either SWIFT Microgateway Microservices, curl script calling SWIFT Microgateway Microservices or SWIFT Microgateway Front-End 2.0.2. You also cannot patch SWIFT Microgateway 2.0.6 to the SWIFT Microgateway 2.17.0-7 following the procedure outlined in the Getting Started Guide (chapter "Applying SWIFT Microgateway Patch Releases") as SWIFT Microgateway 2.17.0-7 is leveraging the new version of configuration database engine which is not compatible with the one used in SWIFT Microgateway 2.0.6

[SWIFT Microgateway 2.17.0-6] - 2023-01-05

Added

  • Support for mgw_supportinfo scripts that collect iformation about the customer environment. It should be run and the output attacheched when opening a support case with Swift.
  • Software name and version of the Microgateway in logfiles and http headers

Removed

  • This version is not available anymore for download. See https://www2.swift.com/knowledgecentre/kb_articles/5025935

[SWIFT Microgateway 2.17.0-2] - 2022-10-20

Added

  • Supporting the new versioning scheme
  • Supporting Java 17 LTS
  • Supporting retries logic in SWIFT Microgateway
  • business_application_profile:
    retries:
    – profile: "trackerProfile"
    initialInterval: 100
    multiplier: 2
    maxInterval: 2000
    httpStatusCode:
    – 429
    – 503
    – profile: "trackerProfile1"
    maxAttempt: 3
    initialInterval: 250
    multiplier: 3
    maxInterval: 5000
    httpStatusCode:
    – 429
    – 500

Changed

  • Relying on Spring Boot 2.6.6
  • Adopting Swagger codegen 3.0.34 for interacting with Central API Repository
  • The new layout of SWIFT Security SDK not dependent on Swagger codegen is used for establishing a secure API session

Removed

  • Support for AIX
  • This version is not available anymore for download. See  https://www2.swift.com/knowledgecentre/kb_articles/5025935

Fixed

  • Fixing the logic used for payloads digest calculation on API responses
  • Fix SWIFT Microgateway 2.x for processing API responses with Unicode characters
  • Improved auto SAG switch over logic in SWIFT Microgateway 2.17.0-1
    .. auto_sag_switch: true auto_sag_cycles: 1 (default) | 2 ..

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.17.0-1

Migration

  • You cannot migrate from SWIFT Microgagateway 1.0.6.x to SWIFT Microgateway 2.17.0-1 automatically. You will have to install and configure SWIFT Microgateway 2.17.0-1 from scratch using either SWIFT Microgateway Microservices, curl script calling SWIFT Microgateway Microservices or SWIFT Microgateway Front-End 2.0.2. You also cannot patch SWIFT Microgateway 2.0.6 to the SWIFT Microgateway 2.17.0-1 following the procedure outlined in the Getting Started Guide (chapter "Applying SWIFT Microgateway Patch Releases") as SWIFT Microgateway 2.17.0.1 is leveraging the new version of configuration database engine which is not compatible with the one used in SWIFT Microgateway 2.0.6

[SWIFT Microgateway 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 Microigateway 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"