Skip to main content
Version: 3.3

Migrating From UDMG 3.2.x

This page outlines the key changes introduced in UDMG 3.3.x when upgrading from UDMG 3.2.x, and explains what happens during migration.

Most changes are applied automatically during the upgrade. However, we recommend reviewing migrated configurations to ensure they behave as expected.

Publish Events: Transition to Tasks and Workflows​

What Changed​

In UDMG 3.2.x, Universal Events were configured directly on each Pipeline using the Universal Event option and related fields.

Publish events were triggered only when a file was received, regardless of whether the transfer succeeded or failed.

Starting in UDMG 3.3.0, Universal Events are implemented through Publish Event Tasks, which are part of Pipeline Workflows.

What Happens on Upgrade​

When upgrading to UDMG 3.3.x, a migration runs automatically on first startup and converts existing publish event configurations:

  • For each Pipeline with the Universal Event option enabled, a Task is created and attached to the Pipeline Workflow.
  • The Task inherits the original Universal Event configuration.

After the migration, the following fields are removed from the Pipeline Record stored in the UDMG database:

  • publish_event_enabled
  • publish_event_name
  • publish_event_credentials_name

The migration is reversible; however, rolling back removes all auto-created Tasks.

Event Types Assignment​

In UDMG 3.2.x, publish events were triggered only when a file was received.

In UDMG 3.3.0, Tasks can be triggered at multiple points in the transfer lifecycle. See Triggers.

During migration:

  • Each Task is assigned to one or more Triggers based on the Pipeline's Source Endpoint and Destination Endpoint.
  • Only Triggers supported by the Pipeline type are considered. See Trigger Availability.

If a Task is not assigned to an expected Trigger, it is likely because that Trigger is not supported for the Pipeline type.

UAC Configuration: HCL vs Task-Level​

Global UAC configuration remains unchanged as is defined in the HCL configuration file (see uac block).

  1. Review migrated Publish Event Tasks by following these steps.
  2. Confirm that each Pipeline Workflow has the expected Tasks in the expected Trigger column by following these steps
  3. Consider adding Tasks for On Staged, On Sent, and On Error Triggers.

Password Policy: Migration to Database-Backed Configuration​

What Changed​

In UDMG 3.2.x, password policy was configured in the Configuration File under the security.password block.

Starting in UDMG 3.3.x, password policy is managed through the UDMG Admin UI.

What Happens on Upgrade​

During the first startup of UDMG 3.3.x, existing password policy values from the Configuration File are automatically migrated to the database.

After migration:

  • The database becomes the single source of truth.
  • Changes to the Configuration File no longer affect password policy.

Migrated Fields​

Only fields previously available in HCL are migrated. New fields introduced in UDMG 3.3.x are initialized with default values. For details, see Password Policy.

FieldMigrated from HCL Argument
Minimum Password Lengthsecurity.password.min_length
Maximum Password LengthNo
Minimum Number of Uppercase Characterssecurity.password.min_upper_case
Minimum Number of Lowercase Characterssecurity.password.min_lower_case
Minimum Number of Numberssecurity.password.min_numbers
Minimum Number of Symbolssecurity.password.min_symbols
Maximum Consecutive Repeated CharactersNo
Password History SizeNo
  1. Review password policy settings by following these steps.
  2. Configure new fields by following these steps.
  3. Remove the security.password block to avoid confusion.

Deprecated Environment Variable​

The following environment variables are deprecated as of UDMG 3.3.x:

  • UDMG_SECURITY_PASSWORD_POLICY_MIN_LEN
  • UDMG_SECURITY_PASSWORD_POLICY_MIN_UPPER
  • UDMG_SECURITY_PASSWORD_POLICY_MIN_LOWER
  • UDMG_SECURITY_PASSWORD_POLICY_MIN_NUMBERS
  • UDMG_SECURITY_PASSWORD_POLICY_MIN_SYMBOLS

These variables are used only during the initial migration, and are ignored after UDMG is upgraded.