# IRPCExtensionAuthentications.LogInAsDifferentUserForExtensionAuthentication

Location: [gRPC API](https://developer.m-files.com/APIs/gRPC-API/index.md) > [Vault API](https://developer.m-files.com/APIs/gRPC-API/vault/index.md) > [Extension authentications](https://developer.m-files.com/APIs/gRPC-API/Reference/MFiles.IRPCExtensionAuthentications/index.md)

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

Badges: `Vault API / standard` `write` `session` `returns metadata structure version`

Asks the external system to start a new login for the caller, so that the caller can switch to
another account there. Used by M-Files clients; applications rarely call it.

- **Service:** [Extension authentications](https://developer.m-files.com/APIs/gRPC-API/Reference/MFiles.IRPCExtensionAuthentications/index.md) `MFiles.IRPCExtensionAuthentications`
- **gRPC method:** `/MFiles.IRPCExtensionAuthentications/LogInAsDifferentUserForExtensionAuthentication`
- **HTTP (mf-http-grpc):** `POST /grpc/v1/log-in-as-different-user-for-extension-authentication`
- **Request:** [`LogInAsDifferentUserForExtensionAuthenticationRequest`](https://developer.m-files.com/APIs/gRPC-API/Reference/MFiles.IRPCExtensionAuthentications/LogInAsDifferentUserForExtensionAuthentication/index.md#request)
- **Response:** [`LogInAsDifferentUserForExtensionAuthenticationResponse`](https://developer.m-files.com/APIs/gRPC-API/Reference/MFiles.IRPCExtensionAuthentications/LogInAsDifferentUserForExtensionAuthentication/index.md#response)
- **Book and level:** Vault API, standard
- **Kind:** write
- **Session:** Required: the session ID from LogIn in the mfiles-session-id-bin metadata.
- **Idempotent:** no
- **Returns metadata structure version:** yes (in the mfiles-metadata-version-bin trailer)
- **Streaming:** none (unary)

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

## Remarks

- Requires a vault session of a user; anonymous sessions fail.
- What happens depends on the external system; any new credentials are stored for the caller.

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

## Request: LogInAsDifferentUserForExtensionAuthenticationRequest

> 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 |
|---|---|---|
| `target` | `string` | The `id` of the target. |

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

## Response: LogInAsDifferentUserForExtensionAuthenticationResponse

No fields.