Feature: Unique Login

Overview

This feature will only allow a user to be logged into one device at a time. If the user successfully logs into a second device, Launcher will force the original device to log out.

Configuration

These values will need to be included in the uniqueLogin section within the Launcher Configuration.

Field	Description
enforceUniqueLogin	boolean When set to true, Launcher will force the authorized user to log out if that user logs in on a different device. Default value is false.
host	string Messaging Service API host. No need to update this setting as it currently defaults to the proper host.
apiKey	string Set to the organization's API key. The API key can be found in the BlueFletch Portal; it is actively managed on the Admin - API Keys page or displayed statically in Manage Organization settings on the Organization page. Note: This field is not needed if using Key Management.

Examples

Using API Key:

{
    ...
    "uniqueLogin": {
        "enforceUniqueLogin": true,
        "apiKey": "--- organization api key ---"
    }
    ...

}

Using Key Management:

{
    ...
    "uniqueLogin": {
        "enforceUniqueLogin": true
    }
    ...

}

Requirements

Unique Login does require the installation and usage of the BlueFletch Messaging application.

Feature Rollout

Unique Login was introduced in Launcher 3.18.10