- 1 Introduction
- 2 Prerequisites
- 3 Baseline
- 4 Architecture
- 5 Swivel Configuration
- 6 Bomgar Configuration
- 7 Testing
- 8 Additional Configuration Options
- 9 Troubleshooting
- 10 Known Issues and Limitations
- 11 Additional Information
This document describes the steps to configure Bomgar with Swivel as the authentication server. Swivel can provide Two Factor authentication with SMS, Token, Mobile Phone Client, It is not currently possible to embed the TURing or Pinpad within the login page/client but these can be provided instead by Taskbar or User Portal for strong Single Channel Authentication.
Swivel 3.x, 3.5 or higher for RADIUS groups
To use the Single Channel Image such as the TURing Image, the Swivel server must be made accessible and the security string provided through the Taskbar, User Portal or other web page, usually through a NAT.
Bomgar Product Version 14.2.2, Product Build 51805, API Version 1.12.0
The Bomgar software makes authentication requests against the Swivel server by RADIUS.
Configuring the RADIUS server
On the Swivel Administration console configure the RADIUS Server and NAS, see RADIUS Configuration
Configuring Two Stage Authentication
The Bomgar client software supports Two Stage Authentication. It is suggested to initially configure just with an OTC and if Two stage authentication is required, configure this once everything has been tested and proven to be working.
Enabling Session creation with username
Setting up Swivel Dual Channel Transports
The following document provided by Bomgar outlines the integration setting on Bomgar: Bomgar RADIUS Integration.
Test the RADIUS authentication
The Bomgar configuration has a test tool, and at this stage it should be possible to authenticate by SMS, hardware Token, Mobile Phone Client and Taskbar to verify that the RADIUS authentication is working for users. Either using the test tool or through the the web login page, and enter Username and if being used, the password. From the Swivel Administration console select User Administration and the required user then View Strings, and select an appropriate authentication string or OTC for the user. At the OTP prompt enter the required OTC. Check the Swivel logs for a RADIUS success or rejected message. If no RADIUS message is seen, check that the Swivel RADIUS server is started and that the correct ports are being used, and is contactable.
If this works then the client software login can be tested.
Bomgar Client login
Bomgar client login uisng Two Stage Authentication
Additional Configuration Options
Known Issues and Limitations
For assistance in Swivel installation and configuration please firstly contact your reseller and then email Swivel Secure support at firstname.lastname@example.org