CPM IDP configuration may fail if CPM is configured with custom DNS

CPM IDP configuration may fail if CPM is configured with custom DNS

When CPM is used with a custom DNS (not AWS DNS or public IP), IDP configuration may fail with the following error in the logs:


Failed getting CPM public host name. Exception: HTTP Error 404: Not Found



If you face this issue, please upgrade to latest 2.2.X version which supports:
  • 'aws-public-ip'
  • 'aws-public-dns'
  • 'aws-private-ip'
  • 'aws-private-dns' or custom address (e.g. rastaman.jm).


Reference defect number – N2WS-740, fixed in v2.2.0a