Uploaded image for project: 'OpenAM'
  1. OpenAM
  2. OPENAM-16587

am-config-upgrader loses IdmIntegrationService configuration

    Details

    • Target Version/s:
    • Needs QA verification:
      No
    • Functional tests:
      No

      Description

      Bug description

      When the am config upgrader tool is run against FRAAS am configs it clears the values set for the IdmIntegrationService config.

      This was seen when upgrading configs from am 7.0.0-7a2542d1eb0c92350a1ef6b36cf8feccea5ca348 to am 7.0.0-726a7b3ff28ae4425660c314fcfd306b0d57f1ee.

      How to reproduce the issue

      #. Obtain a directory of am config suitable for am 7.0.0-7a2542d1eb0c92350a1ef6b36cf8feccea5ca348
      #. Ensure configuration values are set for the IdmIntegrationService
      #. Run the am-config-upgrader against this directory of config
      #. Observe changes that IdmIntegrationService configuration values are set to null

      Expected behaviour
      IdmIntegrationService config values remain set e.g.:
      
          "enabled" : true,
          "idmDeploymentPath" : "openidm",
          "idmDeploymentUrl" : "http://idm.fr-platform",
          "idmProvisioningClient" : "&{rsfilter.provisioning.client.id}",
          "jwtSigningCompatibilityMode" : false,
          "provisioningEncryptionAlgorithm" : "RSAES_PKCS1_V1_5",
          "provisioningEncryptionKeyAlias" : "selfservice",
          "provisioningEncryptionMethod" : "A128CBC_HS256",
          "provisioningSigningAlgorithm" : "HS256",
          "provisioningSigningKeyAlias" : "openidm-selfservice-key"
      
      Current behaviour
      IdmIntegrationService config values are set to null e.g.:
      
          "enabled" : null,
          "idmDeploymentPath" : null,
          "idmDeploymentUrl" : null,
          "idmProvisioningClient" : null,
          "jwtSigningCompatibilityMode" : null,
          "provisioningEncryptionAlgorithm" : null,
          "provisioningEncryptionKeyAlias" : null,
          "provisioningEncryptionMethod" : null,
          "provisioningSigningAlgorithm" : null,
          "provisioningSigningKeyAlias" : null
      

      Work around

      Manually revert the changes to this configuration after running the am config upgrader - Note. this isn't really an option as we want to use the config upgrader as part of our upgrade automation.

        Attachments

          Activity

            People

            • Assignee:
              phillcunnington Phill Cunnington
              Reporter:
              craig.mcdonnell Craig McDonnell
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: