# Account Move/Rename Operation

To enable the account move/rename operation, you must provide the `uniqueAccountAttribute` for the configured LDAP server.

For Oracle Internet Directory (OID), the default Unique Account Attribute (UUID) is `orclGUID`. If your connector uses a custom UUID attribute, specify that attribute instead. You need to configure this attribute using the following API PATCH request:

```json
[
  {
    "op": "add",
    "path": "/connectorAttributes/uniqueAccountAttribute",
    "value": "orclGUID"
  }
]
```

### Handling Binary Attribute for OID

To handle binary attributes for the OID server, the `attributesInBinaryFormat` multi-valued configuration attribute is required. This attribute specifies which LDAP attributes to fetch in binary format.

> [!NOTE]
>
> While this attribute is optional, the `orclGUID` attribute for OID is processed as a binary attribute. Therefore, it is important to configure orclGUID in the `attributesInBinaryFormat` list in addition to setting it as the `uniqueAccountAttribute`.

```json
[
  {
    "op": "add",
    "path": "/connectorAttributes/attributesInBinaryFormat",
    "value": ["orclGUID", "<binary attribute 2>"]
  }
]
```

### Provisioning for Move and Rename Operations

To handle move and rename operations, you need to send special provisioning attributes in an AttributeRequest. The following table lists the special attributes to handle the move and rename operations.

| Attribute | Description |
| --- | --- |
| AC\_NewName | A string attribute that specifies the new name for the user. For example, cn=abc,uid=xyz |
| AC\_NewParent | A string attribute that specifies the new organizational unit (OU) for the user. For example, ou=xyz,dc=pqr,dc=com |