Broadcom: API Gateway - Revision versions and comments are gone after migrating policies via GMU
search cancel

Broadcom: API Gateway - Revision versions and comments are gone after migrating policies via GMU

book

Article ID: 260830

calendar_today

Updated On:

Products

CA API Gateway

Issue/Introduction

Using Gateway Migration Utility (GMU) to migrate items from Gateway to Gateway may require manual interaction post execution and some limitations are applied. 

In this particular example, customer's noticed that policy versions (and all their comments) existing in the source Gateway are not found in the destination one.

Environment

API Gateway 10.x/11.x

Cause

GMU comes with some limitations, specifically for the following items:

  • LDAP user certificates
  • Internal user password history
  • Group membership data
  • FIPs virtual groups
  • Private key special purpose flags
  • Default HTTP proxy settings
  • Policy versions and their comments
  • Custom and modular assertions
  • Default password rules
  • Service resolution configurations
  • Licenses
  • Log sink configuration
  • Metrics and audits
  • Kerberos configurations
  • HSM private keys
  • Cluster wide property when used in an encapsulated assertion 

Resolution

In the product guide, we have published a section in where we document limitation from GMU and what additional tasks need to be completed after running the migration.

Manage Migration Limitations