Behavioral changes in Cloudera Migration Assistant

Behavioral changes denote a marked change in behavior between Cloudera Migration Assistant releases. This topic covers 4.1.0.

Cloudera Migration Assistant 4.1.0

Summary: User-scoped connections for Git and workloads: Previous behavior:
Cluster and migration credentials were configured primarily through administrator settings and agent configuration, not per user in the UI.; New behavior:
Users create User Connections on eligible clusters. Scans and migrations resolve credentials for the active user from Vault-backed connection records. See Managing user connections.
Summary: Agent connections for Cloudera Manager and control plane endpoints: Previous behavior:
Agent credentials for Cloudera Manager and related control plane endpoints were tied to cluster registration or agent configuration files.; New behavior:
Administrators manage agent connections on the Connections page. Clusters registered in 4.1 receive connections automatically; upgraded deployments require manual connection setup for clusters registered before 4.1. See What's new and Registering clusters.