> ## Documentation Index
> Fetch the complete documentation index at: https://syteca.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# One-Time Passwords

> Require a Windows Client login to be approved with a one-time password, either through an Approver or sent automatically to trusted users.

<Note>
  Applies to Windows Clients only.
</Note>

One-time passwords add an extra layer of protection to Windows Client logins by requiring a user to request (and enter) an additional password before they can access the computer. A designated **Approver** processes the request, or - if configured - the password is generated and emailed automatically without requiring approval.

<Warning>
  The **Enable secondary user authentication on login** and **Allow the use of one-time passwords** options cannot be used together. Neither works correctly if both checkboxes are selected. See [Secondary user authentication](/docs/administration/clients/parameters/secondary-user-authentication) for the alternative.
</Warning>

## Enable one-time passwords

<Steps>
  <Step title="Open the Client or Client Group">
    Log in to the Management Tool as a user with the [Client Configuration Management permission](/docs/administration/users/client-permissions). Click **Clients**, then find the Client or Client group to configure and click its name.
  </Step>

  <Step title="Allow one-time passwords">
    On the **Editing Client** (or **Editing Client Group**) page, select the **Authentication Options** tab, scroll to **Two-Factor and Secondary Authentication**, and select **Allow the use of one-time passwords**.
  </Step>

  <Step title="Select Approvers">
    In **Users who can approve access**, select every user who should be able to approve one-time password requests.

    <Note>
      Approvers can process a request either by clicking the link in a notification email (if they have an email address on file), or on the **Access Requests** page's **Access Requests** tab in the Management Tool. A request that isn't processed within 30 minutes automatically expires by default - adjustable on the **System Settings** tab of the Configuration page.
    </Note>
  </Step>

  <Step title="Optionally enable automatic delivery">
    To skip Approver review entirely for certain users, select either:

    * **Automatically send one-time passwords to Active Directory users** - requires an email address defined on each such user's Active Directory account.
    * **Automatically send one-time passwords to internal users** - requires an email address on the internal user's **User Details** tab, and the **Access to Endpoint via Secondary Auth.** permission granted on their **Client Access** tab.
  </Step>

  <Step title="Save">
    Click **Finish**.
  </Step>
</Steps>

<Frame caption="The Two-Factor and Secondary Authentication section with one-time passwords enabled.">
  <img src="https://mintcdn.com/syteca/0FlD-vkHsBA1azVX/images/administration/clients/parameters/one-time-passwords-config.png?fit=max&auto=format&n=0FlD-vkHsBA1azVX&q=85&s=0ffee5d4ac3771e0c7a9ba14f9521056" alt="Authentication Options tab showing one-time password settings" width="1900" height="1070" data-path="images/administration/clients/parameters/one-time-passwords-config.png" />
</Frame>

## Approve or generate a one-time password

When a user requests access, the request goes to every configured Approver by email and appears on the **Access Requests** page's **Access Requests** tab.

<Tabs>
  <Tab title="Approve a pending request">
    <Steps>
      <Step title="Open Access Requests">
        Log in to the Management Tool as a listed Approver and click **Access Requests**.
      </Step>

      <Step title="Approve the request">
        Click **Approve** next to the relevant request, optionally enter a comment, and click **Confirm**.
      </Step>

      <Step title="Password is emailed">
        A one-time password is generated and sent automatically to the user's email address.
      </Step>
    </Steps>
  </Tab>

  <Tab title="Generate without a request">
    <Steps>
      <Step title="Open the generation dialog">
        On the **Access Requests** page, open the drop-down next to the **Access Requests** tab and select **Generate Password**.
      </Step>

      <Step title="Fill in the details">
        In the **One-Time Password Generation** window, select the **Client name**, enter the **User name** (or domain name for Active Directory users), and the **User's confirmation email** the password should be sent to. Optionally edit the default **Comments** text ("Generated without request").
      </Step>

      <Step title="Generate">
        Click **Generate**. The password is sent automatically to the specified email address.
      </Step>
    </Steps>
  </Tab>
</Tabs>

## Request and log in with a one-time password

This is the end-user flow - what a user sees when they log in to a Client with one-time passwords enabled, as opposed to the admin setup or Approver-initiated generation covered above.

<Steps>
  <Step title="Log in to Windows normally">
    Locally or remotely, as usual.
  </Step>

  <Step title="Request a one-time password">
    The Client shows a pop-up asking for a one-time password. Click **Request One-Time Password**.
  </Step>

  <Step title="Provide identifying details">
    A second pop-up appears, depending on which automatic-delivery options are enabled:

    * **Neither automatic option enabled** - enter an **Email** address, then click **Request**.
    * **Automatically send to Active Directory users** enabled - just click **Request**.
    * **Automatically send to internal users** enabled - enter the internal Management Tool **Login** and **Password**, then click **Request**.

    <Tip>
      In either of the last two cases, the user can instead select **I need emergency access to computer** and enter an email address manually.
    </Tip>
  </Step>

  <Step title="Receive the password by email">
    A confirmation message appears, and the one-time password arrives by email.
  </Step>

  <Step title="Enter the password">
    Back on the first pop-up (now showing the email address automatically), enter the received password.
  </Step>

  <Step title="Access is granted or denied">
    The credentials are validated against the Application Server. If the email and password match, and the password was generated for this user and this Client, access is granted - otherwise the user sees a denial message.
  </Step>
</Steps>

Once logged in, the Client records the session under `<Windows account> (<email address>)` in the **Client Sessions** list's **User Name** column.

<Note>
  A one-time password works only once, only within the [Access Request Expiration Time](/docs/administration/configuration/system-settings#expiration-time-of-access-requests) (default 30 minutes), and only for the Client it was requested from. If it expires or needs resending, the user can request again - but no more than once per hour for the same Client.
</Note>

## Related

<CardGroup cols={2}>
  <Card title="Secondary user authentication" icon="user-check" href="/docs/administration/clients/parameters/secondary-user-authentication">
    An alternative, mutually exclusive login-identification method.
  </Card>

  <Card title="Client permissions" icon="shield" href="/docs/administration/users/client-permissions">
    Permissions required to configure Clients and approve access.
  </Card>

  <Card title="Windows Clients" icon="windows" href="/docs/administration/clients/windows">
    Windows Client installation and configuration.
  </Card>

  <Card title="System settings" icon="settings" href="/docs/administration/configuration/system-settings">
    Change the default request expiration time.
  </Card>
</CardGroup>
