Access types are connection methods uses to access an asset using an interface. Sectona platforms support a range of access types and to provide multiple types of access types pre-bundled with the system. The system supports access types over browser launched on local machines or accessed over a jump server.
Access types can be managed in Configuration → Plugins & Connectors → Access types. If the option is selected Enforce Access via Jump Server, all access will be routed to the jump server. Native RDP client-based access can be invoked if Allow RDP client is selected.
User access policy also allows access to be moved over the jump server. In that situation, all access will be routed over the jump server irrespective of access type policy definition.
Linking asset type with access type
Access type linking to asset types can be managed in Configuration → Asset type → Select the Asset → Navigate to Linked Access type. Select the desired access type you want to link to a specific access type.
Modifying existing access type parameters
Navigate to Configuration → Plugins & Connectors → Access types.
Select the desired access types.
Configure parameters including Base Access type, Default ports, Additional ports or Plugin process.
To disable the access type across the platform, unselect Active box.
Use these settings with caution as these may change the way system managed access types.
Adding a new access type
To add a new access type, you may follow these steps:
Navigate to the "Configuration" section in the navigation bar.
Click on the "Access type" in the sidebar.
Click on the "+New Access type" button. A form will appear in front of you fill in the credentials.
Name: Define a suitable unique name for the access type.
Base Access type: Select any one of the base access types available for integration
Default port: The default port for the access type will be provided.
Additional Ports: To allow additional ports for the access type.
Click on the "Save" button and your access type will be created.
For access types selected as thick clients, a plugin process file must be provided. To learn how to create a new plugin process access more information by clicking here.
For configuring custom browser-based URL integration, click here.