For the complete documentation index, see llms.txt. This page is also available as Markdown.

Configuration Guide

The Launcher is configured by a single JSON file:

C:\ProgramData\BlueFletch\launcher.json

The file is validated against a JSON schema every time it changes. If validation fails, the Launcher shows a Configuration Error screen naming the failing property, and it will not start a session until the file is corrected.

A new configuration takes effect the next time the Launcher returns to the login screen (after a logout); in Open Zone mode the session is cycled automatically.

Building Configuration

You can find reference sample configurations in the folder C:\Program Files\BlueFletch\BlueFletch Launcher\resources\config (only available after installation). The file names can help you identify the configuration best suited for your company's IDP and reauthentication method (e.g. launcherCentralAuthNFC_OKTA_WAVEID.json means Okta IDP with RFIdeas badge reader and Cental Auth Server).

Please note that it is not required to specify configuration during installation and you can reference the aforementioned folder to build your dedicated configuration after application installation.

Visit Technical Guide to find details on configuration fields and to help you modify sample configuration files based on your company's needs.

Applying Configuration

If you need to define and/or modify configuration post installation, you can do so by saving or updating launcher.json file in this location: C:\ProgramData\BlueFletch\.

This can be done manually or using the following script:

Replaces the configuration on an installed device without reinstalling:
C:\Program Files\BlueFletch\BlueFletch Launcher\resources\setup-scripts\BFEWindowsLauncher_configUpdate.ps1 -ConfigPath "C:\path\to\launcher.json"

Last updated