maayant

Hi Hubert,

I'm happy we could help pinpointing this issue faster.

I've tested the updated add-on and both issues are fixed. Password is automatically filled, and when starting a new OpenVPN the previous process is killed as expected.

Thanks for the quick fix.

Hi,

Access information to a password-based environment was sent via email.

Regards.

Hi,

Yes, as I wrote, I've tried with both RDM and OpenVPN running as administrator, and both running as a normal user.

If you need a password-based environment please let me know, I can probably arrange one quickly.

Greetings,

OpenVPN version 2.4.0-I601.

RDM version 12.0.8.0 64-bit.

OpenVPN Add-on version 2.4.0.0.

OpenVPN 2.4 was released a few days ago, with some major changes to the GUI. As a result the RDM OpenVPN addon is no longer able to enter the key password with "Enable automatic key password entry" option enabled (note that username/password via "Enable automatic authentication" does work), nor killing the OpenVPN process with the "Kill existing OpenVPN session before connection" option enabled.

In addition, it seems like sometime ago we have lost the icon to show passwords (eye icon) in the OpenVPN addon.

There might be other issues, I haven't tested everything.

Tried with both RDM + OpenVPN run as administrator and RDM + OpenVPN run as normal user.

Thanks.

Great news.

Thanks!

Hi,

I've mentioned this in the past to Mr. Maurice Cote.

An OpenVPN addon that is based on the OpenVPN CLI binary and not the GUI will make it easier to deploy RDM in an organization.

Today the OpenVPN addon is based on the GUI client, forcing all RDM users to authenticate with the same keys and usernames/passwords in order to connect to a remote server.

Using the CLI binary (and allowing MARCOs) will make it possible to use a per user key and username/password.

OpenVPN binary manual: https://community.openvpn.net/openvpn/wiki/Openvpn23ManPage

Similar in functionality to the already existing addons for HP "iLO", remotely managing various aspects of the server hardware, in addition to being able to get a remote console will be great.

Dell iDRAC API: http://en.community.dell.com/techcenter/extras/m/white_papers/20206135

Hi,

It would be great to be able to directly control Linode virtual machines.

Linode API here: https://www.linode.com/api

Hi,

I'm using XenCenter version 6.2 (build 1377).

I have no problem connecting with it to any of the above XenServer versions.

I've done further tests.

I am able to connect to XenServer 6.1.

For XenServer 6.0.2 I'm getting the following error in the Application Log:

----------------------------------

System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary.

at System.Collections.Generic.Dictionary`2.get_Item(TKey key)

at Devolutions.CitrixInterface.XenServerManager.GetHost(Session session)

----------------------------------

I'll need to do some more tests with 6.2 as well.

Hi,

RDM 10, I'm unable to connect using XenServer session to either XenServer ver 6.0.2, 6.1 nor 6.2, while connecting without a problem using XenCenter. Haven't tested it with other XenServer versions.

Nothing shows in the application logs.

I've followed the forum posts below, trying both port 80 and 443, using different methods of authentication, alas the result is always the same.

http://forum.devolutions.net/topic2307-xenserver-not-working.aspx

http://forum.devolutions.net/topic2260-adding-xenserver-host-entry.aspx

Thanks.

Thanks André,

As you suggested, we will use PuTTY session until its fixed.

Also, while at it, I would like to suggest adding the ability to set more than one tunnel per session settings.

Hi,

To create the tunnel I'm using RDM built-in SSH.

Add > Add Session > Telnet, SSH, Raw, rLogin.

In the drop down list I select "SSH".

In the Host I'm entering my remote Linux server IP address to create the tunnel on.

In the "Outgoing Tunnel Settings":

Local IP: 127.0.0.1

Port: Local port to bind to (i.e 7138)

Remote Host: IP of remote host to create tunnel to

Remote Port: 22

Then I create another Session as above, but instead of "SSH" I select "PuTTY", and enter host to connect: localhost, port: 7138. This way everything works as expected.

If instead of "PuTTY" I select "SSH Shell" with the same parameters it will just time out, unable to connect.

Hey André,

Yes, I've built the tunnel with the built-in SSH functions (no PuTTY involved in creating the tunnel).

After the tunnel is created we are unable to use the built-in SSH Shell to go through it, yet we are able to go through it with an embedded PuTTY session.

Greetings,

We are evaluating RDM 10 Enterprise.

It seems like there is a problem connecting to an SSH tunnel with the built-in SSH shell.

I've created an SSH connection, with a tunnel from localhost port 7058 to remotehost.example.com port 22.

We are able to connect with an embedded PuTTY session without a problem to localhost port 7058, yet its not working with the built-in SSH shell session. I cannot find any guide or how-to on this subject, am I doing anything wrong? Or is it really a bug?

Thanks in advance.

Thanks.

We've managed to use the basic OpenVPN addon for multi-user by naming the ovpn file for each site the same in every computer, and rename the pkcs12 file as [username].pkcs12, we then used the $USERNAME$ variable in the pkcs12 file name field in RDM.

This is a pretty ugly solution, and forces our RDM users to change file names for existing and new vpn tunnels. A much better way will be to be able to set "User Specific Settings" in the RDM OpenVPN module of course.

Hi,

We are evaluating RDM 10 enterprise.

While testing the application and reading posts here on the forum I've noticed you are invoking OpenVPN tunnels using the openvpn-gui.exe .

I was wondering why not use the openvpn.exe executable instead, as it has many more features and options, including allowing a better implementation for multi-user environments, and with the added benefit of bypassing known openvpn-gui bugs such as defaulting the passphrase window to RTL language (if an RTL language is installed), its annoying tray icon that never dies unless you move your cursor over it. This might also resolve the must run as administrator problems I've seen in some posts here.

As a very simple example that mimics the openvpn-gui connection:

C:\Program Files\OpenVPN\bin\openvpn.exe --config "C:\Program Files\OpenVPN\config\SITENAME\configname.ovpn" --pkcs12 "D:\Program Files\OpenVPN\config\SITENAME\pkcsfile.p12"

Now just pass the passphrase to it.

To see the full list of options: openvpn.exe --help

Thanks.

edited by maayant on 9/23/2014

Thanks!

The "GRANT" priv was missing, now the "admin" user can create new users successfully from within RDM.

Thanks.

Just to make it clear, I am using RDM to create the users, but trying to create Data Source for each new user fails, unless I'm connecting to the DB and manually granting privs:

MariaDB [(none)]> grant all on rdm.* to 'newuser'@'%';

MariaDB [(none)]> FLUSH PRIVILEGES;

Hi,

We are evaluating RDM 10. I've created a new user in MariaDB, lets call it "admin" and granted it all privileges on *.*. Flushed privileges.

I used this admin account as the user for the Data Source, created the schema successfully, named it "rdm".

When creating a new user, I can see the user in the mysql "user" table, but the user is unable to connect to the rdm database. The problem seems to be that there are no privileges granted to that new user on the "rdm" database (rdm.*). Please advise.

In addition, can you please specify what are the exact privileges required for a user on the rdm db? I'm worried because, for example, if a user have the Drop privilege s/he can connect directly to the DB with a MariaDB client and just drop it. This is possible because their RDM username and password are known to them, and are the same for their MariaDB user. If this is indeed the case, can you please advise on how should I protect the database?

Thanks in advance.