# IRPCVaultAdmin.MigrateAuthenticationConfiguration

Location: [gRPC API](https://developer.m-files.com/APIs/gRPC-API/index.md) > [Administration API](https://developer.m-files.com/APIs/gRPC-API/admin/index.md) > [Vault administration](https://developer.m-files.com/APIs/gRPC-API/Reference/MFiles.IRPCVaultAdmin/index.md)

HTML version: https://developer.m-files.com/APIs/gRPC-API/Reference/MFiles.IRPCVaultAdmin/MigrateAuthenticationConfiguration/

Badges: `Administration API / specialized` `internal: not for applications` `admin` `session`

Migrates one authentication configuration of the vault to the current format after a successful
test sign-in with it.

- **Service:** [Vault administration](https://developer.m-files.com/APIs/gRPC-API/Reference/MFiles.IRPCVaultAdmin/index.md) `MFiles.IRPCVaultAdmin`
- **gRPC method:** `/MFiles.IRPCVaultAdmin/MigrateAuthenticationConfiguration`
- **HTTP (mf-http-grpc):** `POST /grpc/v1/migrate-authentication-configuration`
- **Request:** [`MigrateAuthenticationConfigurationRequest`](https://developer.m-files.com/APIs/gRPC-API/Reference/MFiles.IRPCVaultAdmin/MigrateAuthenticationConfiguration/index.md#request)
- **Response:** [`MigrateAuthenticationConfigurationResponse`](https://developer.m-files.com/APIs/gRPC-API/Reference/MFiles.IRPCVaultAdmin/MigrateAuthenticationConfiguration/index.md#response)
- **Book and level:** Administration API, specialized
- **Kind:** admin
- **Session:** Required: the session ID from LogIn in the mfiles-session-id-bin metadata.
- **Idempotent:** no
- **Returns metadata structure version:** no
- **Streaming:** none (unary)

<a id="remarks"></a>

## Remarks

- **For M-Files components only.** M-Files Admin calls it after the administrator has tested the
  migrated configuration by signing in. Applications should not call it.
- Requires a vault session with full control of the vault.
- `auth_data` is the result of the test sign-in in M-Files' own binary format. The call fails if
  the sign-in data does not validate against the migrated configuration.

<a id="request"></a>

## Request: MigrateAuthenticationConfigurationRequest

> Nested message fields are expanded to depth 3; follow a type link for deeper levels and for the type's own page.

| Field | Type | Description |
|---|---|---|
| `configuration` | [`AuthenticationConfigurationMigration`](https://developer.m-files.com/APIs/gRPC-API/Reference/Messages/MFiles.AuthenticationConfigurationMigration/index.md) | The configuration to migrate, as returned by [GetMigrantAuthenticationConfigurations](https://developer.m-files.com/APIs/gRPC-API/Reference/MFiles.IRPCVaultAdmin/GetMigrantAuthenticationConfigurations/index.md). |
| `configuration.scope` | `string` | Scope of the configuration. |
| `configuration.original_name` | `string` | Name of the original configuration. |
| `configuration.migrated_configuration` | `string` | Configuration in migrated form. |
| `configuration.entra_id_tech_cred` | `bool` | Is the original configuration for Entra ID with technical credential settings included. |
| `auth_data` | `bytes` | Authentication data from the test sign-in with the migrated configuration. |

<a id="response"></a>

## Response: MigrateAuthenticationConfigurationResponse

No fields.