Smartcard Bridge (Native Client)
Kasm Smartcard Bridge (Native Client) is a Windows/MacOS application and Chrome extension that works together to enable passing a smartcard connected to a local machine into a Workspace.
System Requirements
- Windows
- macOS
| Supported Operating Systems |
|---|
| Windows 10 (x86_64) |
| Windows 11 (x86_64) |
| Windows Server 2019 (x86_64) |
| Windows Server 2022 (x86_64) |
| Windows Server 2025 (x86_64) |
| Supported Operating Systems |
|---|
| MacOS Sonoma (Intel/Apple Silicon) |
| MacOS Sequoia (Intel/Apple Silicon) |
| MacOS Tahoe (Intel/Apple Silicon) |
Installation
The Kasm Smartcard Bridge can be installed using one of the installers below which places all the necessary files in C:\Program Files\Kasm on Windows and '/Library/Application Support/Kasm' on MacOS. You should use the latest version that supports the version of Kasm Workspaces you have installed.
- Windows
- MacOS
| Installer Version | Installer Link | Kasm Workspaces Compatibility | SHA256 |
|---|---|---|---|
| Developer Preview | Kasm_Smart_Card_Bridge_develop_1.0.4304bc51.msi | Developer Preview | rolling |
| 1.0.4304bc51 | Kasm_Smart_Card_Bridge_1.0.0_1.0.4304bc51.msi | 1.18.0 | 3b0a58c2950927b53e1668990a3a47ff29d08cc0cf91acc01482b6c5ad572104 |
| Installer Version | Installer Link | Kasm Workspaces Compatibility | SHA256 |
|---|---|---|---|
| Developer Preview | Kasm_Smart_Card_Bridge_develop_1.0.4304bc51.signed.pkg | Developer Preview | rolling |
| 1.0.4304bc51 | Kasm_Smart_Card_Bridge_release_1.0.4304bc51.signed.pkg | 1.18.0 | 3f089e73a08233aad7be037d5f46a4d9ffeabdcdcc3e949cbe8c85ffbb8f001a |
The Developer Preview Build of the Kasm Smartcard Bridge Service listed above should only be used with the developer preview build of Kasm Workspaces on non-production systems.
The documentation on this page is for the latest version of the installer listed in the table above and may not be accurate for older versions.
Installation Troubleshooting
During the installation on Windows, the Kasm Smartcard Bridge installer will attempt to add a path to a config file at: 'HKLM\SYSTEM\CurrentControlSet\Services\EventLog\Application\KasmSmartCardBridge' in the Windows Registry. If endpoint security softwer is configured to prevent installers from editing the Windows Registry, the install may fail.
Upgrade
When running the installer on a machine with an existing Kasm Smartcard Bridge an upgrade will be performed.
You should close all of your browser windows prior to updating the Kasm Smartcard Bridge.
Uninstall
- Windows
- macOS
If the Kasm Smartcard Bridge needs to be uninstalled it can be removed by going to Add or remove programs / and selecting the Kasm Smartcard Bridge and then selecting Uninstall.
There will be a dialog box asking you to confirm you wish to remove the Kasm Smartcard Bridge, click OK to continue.
You can manually remove the folder/file or use the uninstaller:
Folder: /Library/Application Support/Kasm/Smart Card Bridge
File: /Library/Google/Chrome/NativeMessagingHosts/com.kasm.smartcard.json
Uninstaller: Kasm_Smart_Card_Bridge_Uninstaller
Logging
By default, only warring and error log messages are written to Windows event log (under Applications->KasmSmartcardBridge) or the MacOS syslog, and all log messages
are written to log files on the local machine.
- Windows
- macOS
Log file path: %APPDATA%\Kasm\Smart Card Bridge\logs\kasm_scard_bridge.log
Alternative log file path: C:\temp\kasm-logs\kasm_scard_bridge.log
Log file path: ~/Library/Logs/Kasm Smart Card Bridge/kasm_scard_bridge.log
Alternative log file path: /tmp/kasm-logs/kasm_scard_bridge.log
The alternative log file path is used when the Smartcard bridge is unable to write to the normal log path. This is usually due to the Smartcard Bridge not having write permissions to the desired folder.
A new log file is generated each time the Smartcard Bridge is launched, or when the active log file reaches a size of 10 MB. The system maintains a maximum of four log files. Once this limit is reached, the Smartcard Bridge will overwrite the oldest log file with a new one, ensuring that only the four most recent log files are retained.
but can be also redirected to a file by specifying the log_file parameter in config.yaml. Logs are also sent to the Kasm Workspaces deployment and can be searched for the Kasm Admin UI under Diagnostics->Logging.