# Breaking changes

Documentation owner: product `control`; documentation version: `next`.
Source: `content/products/control/next/the-service/about-this-release/breaking-changes.md` at commit `eaf7a020437971baeee95e87eaf963636040ac71`.

## 1.2.0

There are no known breaking changes in Control 1.2.0.

## Earlier changes

### LDAPModify skips empty replace operations when `ignore_empty_values` is enabled

`LDAPModify` no longer fails when all attributes in `replace` are empty and `ignore_empty_values` is set to `true`.

Previously, `LDAPModify` skipped individual empty values when at least one replacement attribute had a value, but failed when all replacement attributes were empty. The behavior is now consistent: empty replacement values are ignored in both cases when `ignore_empty_values` is enabled.

Review configurations that relied on this failure to stop a flow. If a flow must fail when all replacement attributes are empty, add explicit validation before `LDAPModify`.

### Only updated values are sent to pipe

Data changed by user will be sent to pipe.

### Updated default encryption

As of 3.1.1, the default encryption has changed. This only affects systems where encryption is enabled.

To keep previous implementation ensure environment setting:

FORTIFIED\_SECRETS\_IMPL = local