Tenant Connector

the tenant connector provides secure remote data center connections to different tenants who want to use single connect’s features, such as preventing password theft and eliminating unsupervised access and need a secure connection between their remote data centers and the central single connect server this section describes how the tenant connector is added and matched with devices to create an openvpn connector adding an openvpn connector tenants who already have an openvpn server in the remote data center or want to use openvpn in their remote data center connections can use this feature navigate to tenant connector open the connector sites tab click the add button, enter the remote site name and description, and click save open the connector nodes tab click the add button and select the openvpn option select the connector site, enter the openvpn credentials, copy the openvpn configuration, and click save adding a built in vpn connector tenants who do not have an openvpn license and want to use single connect’s secure connection can use its built in vpn option connectorinstallation packages are uploaded tofilerepo krontech com sftp server the kron support team provides credentials and the ova installer filename refer to the tenant connector reference guide to create a built in vpn connection navigate to tenant connector open the connector sites tab click the add button, enter the remote site name and description, and click save open the connector node tab click the add button and select the built in vpn option select the remote site name, enter the node name, tunnel port, connection port, connector node external ip, the ssh rsa key created during the connector node installation, and click save connector monitoring connectors send heartbeat messages to single connect servers at regular intervals this information can be used to monitor whether the connectors are working properly to check the heartbeat messages navigate to tenant connector open the connector nodes tab click the list view button, select the connector node, and click the heartbeat button adding a device to a connector site in order to access the devices located at remote data centers through the connector, these devices must be associated with the connector sites to associate a device with a connector site navigate to device management > device inventory click the new device discovery button fill out the relevant device information, select the connector site, and save by clicking discover and add adding sapm accounts if you haveaconnector in your environment, everysapmaccountrequest(check password, reset password etc )isrun overthe connectorserver the connector supports winrm, ssh, ssh keys,ldapsand databases(e g , mysql, oracle, teradata) some accounts (for example ad/ldaps, mysql)need to edit on sapm configuration ldaps ad hostname with fqdn, ${deviceport} ldaps\ //windows server0 krontech test ${deviceport} you must add connector ip in the hosts file of sc example(192 168 0 1 windows server0 krontech test) ldap port 636 mysql ${deviceip}, ${deviceport} jdbc\ mysql //${deviceip} ${deviceport}/testdb ldap/ad integration via connector site enter the related configuration parametersand select the connector site name on ldap advanced filterthenclick the save button refer to docid\ xzxpft2moexwpjykoxda5 siem integration via connector site add the parameter name is syslog connector sitename and value is your connector site name in the system config man refer to docid 15r5ajku0sb7wk7 kcaim