LDAP : Configure and Import LDAP Groups in VBrick Rev : Edit and Run the LDAP Connector Runtime Files
  
Edit and Run the LDAP Connector Runtime Files
Included with your VBrick Rev installation are two files that are used in conjunction with importing LDAP groups.
 
They are:
VBrickPlatform.LdapConnector.Runtime.exe
VBrickPlatform.LdapConnector.Runtime.exe.config
Before you are able to import LDAP groups, you must first modify the config file and then run the executable file so that you are ready to import (or sync once you have your groups imported).
 
Tip: The editing steps described in this topic will not be necessary if you have the Direct Connection checkbox selected on your LDAP Connector. You may instead begin directly importing your LDAP groups.
 
Edit the LDAP Connector Runtime Config File
Edit the VBrickPlatform.LdapConnector.Runtime.exe.config file using any text editor. It will look similar to the configuration code below.
There are three lines that will be modified in the <appSettings> block:
<add key="RuntimeUrl" value="http://rev.avenger.com:12345" /> (required)
<add key="ApiKey" value="SomeMagicKey" /> (required)
<add key="RetryTimeInSeconds" value="5" /> (optional)
 
<?xml version="1.0" encoding="utf-8"?>
<configuration>
<startup>
<supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.5" />
</startup>
<appSettings>
<add key="ServiceName" value="VBrick Rev LDAP Connector" />
<add key="RuntimeUrl" value="http://rev.avenger.com:12345" />
<add key="ApiKey" value="SomeMagicKey" />
<add key="RetryTimeInSeconds" value="5" />
</appSettings>
<runtime>
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
<dependentAssembly>
<assemblyIdentity name="Microsoft.Owin" publicKeyToken="31bf3856ad364e35" culture="neutral" />
<bindingRedirect oldVersion="0.0.0.0-2.0.2.0" newVersion="2.0.2.0" />
</dependentAssembly>
<dependentAssembly>
<assemblyIdentity name="Microsoft.Owin.Security" publicKeyToken="31bf3856ad364e35" culture="neutral" />
<bindingRedirect oldVersion="0.0.0.0-2.0.2.0" newVersion="2.0.2.0" />
</dependentAssembly>
<dependentAssembly>
<assemblyIdentity name="System.Reactive.Interfaces" publicKeyToken="31bf3856ad364e35" culture="neutral" />
<bindingRedirect oldVersion="0.0.0.0-2.2.4.0" newVersion="2.2.4.0" />
</dependentAssembly>
<dependentAssembly>
<assemblyIdentity name="System.Reactive.Core" publicKeyToken="31bf3856ad364e35" culture="neutral" />
<bindingRedirect oldVersion="0.0.0.0-2.2.4.0" newVersion="2.2.4.0" />
</dependentAssembly>
<dependentAssembly>
<assemblyIdentity name="System.Reactive.Linq" publicKeyToken="31bf3856ad364e35" culture="neutral" />
<bindingRedirect oldVersion="0.0.0.0-2.2.4.0" newVersion="2.2.4.0" />
</dependentAssembly>
</assemblyBinding>
</runtime>
</configuration>
 
Modify the <add key="RuntimeUrl" value="http://rev.avenger.com:12345" /> to reflect the URL of your Rev installation. This may be obtained from your browser bar address. This is a required edit to the config file.
Modify the <add key="ApiKey" value="SomeMagicKey" /> to reflect the API key value you created for the LDAP Connector. All devices in Rev must have a corresponding API key associated to them including LDAP Connectors. This is a required edit to the config file.
You may also modify <add key="RetryTimeInSeconds" value="5" /> to reflect the number of times (in seconds) the executable file will wait before attempting to reconnect when it has disconnected. The default setting is 15. This edit is optional.
Save the config file with your changes.
 
Run the LDAP Connector Runtime Executable File
Once the VBrickPlatform.LdapConnector.Runtime.exe.config file has been edited correctly, use a command prompt and run the VBrickPlatform.LdapConnector.Runtime.exe file with the /console parameter. Your output should look similar to the following:
 
C:\users\user.name>"C:\Users\user.name\desktop\LDAP 2\VBrickPlatform.LdapConnector.Host.exe" /console
 
Starting connector...
 
Press any key to stop...
Starting with MAC Address: 843A4B2368A4
API Key authenticated...
 
Connection Established
 
Message Received: LdapConnectorDeviceConnectionRecorded
Dispatching SynchronizeLdapGroups
Subscribing to route: bde1e55d-5d41-4ba5-bde4-30882289db4f
Message Received: AvailableLdapGroupsSynchronized
 
This executable should now always be running (to import and synchronize LDAP groups) and you are ready to import.
 
*See Also:
Import an LDAP Group