maikeltonissen

Yes, fix confirmed

Oke, when are you expecting to release this?

Whenever we access a record with contains a Keeper entry, the system errors our with an overflow exception and we cannot retrieve the passwords.

Multiple users in our office have the same issue currently.

Is there any update on this matter? I know it's a month ago but for our use-case this missing feature is becoming the dealbreaker on using the gateway.

We are unable to prevent users from different projects to access each others projects with this issue and it's not good enough to pass ISO27001 for that matter.

Hi Maikel,

We are working on providing RPM builds and repositories. What version of RHEL/Rocky are you using?

Best,

Allan

Hello Allan,

We are currently using Rocky 9.5.

Hi Maikel,

Thank you for the detailed use case.

Can you tell me which one of DVLS or Hub you are using?

I believe your use case is similar to this one: https://forum.devolutions.net/topics/43431/gateway--network-segregation--group-based

We have an internal ticket for this feature, and we are currently considering its implementation for the next iteration. (Initially, the feature would be implemented for DVLS, and Hub would come later.)

I’ll add your request to back it up.

I’ll let you know when there is an update on it!

Have a great day,

We are using the Devolutions Hub Business, all users use RDM.

Hello,

I might have an interesting usecase which i'm not sure there is a solution for yet, if there is I would like to know.

We have saveral vaults, actually a vault for each in-house project we have. Each of these vaults have specific users in them which maintain(create/read/update) the entries. I did it this so so that the projectowner can maintain the vault and I don't have to maintain every vault individually after the inital creation. All these users are synced with Entra ID, but that's not relevant to my issue.

We have three physical offices currently and each office has an on-premise Devolutions Gateway running in the DMZ. This DMZ subnet connects through our company firewall with each seperate subnet(VLAN) which houses a project. This works perfectly but it seems I just made a massive security gap which I missed initially.

Each user can create his/her own entry in their vault, I can limit their gateway selection if I want too but what i cannot seem to limit is which subnet(vlan) the user is able to connect to when he/she establishes a connection.

For example:

Office A houses projects 1, 2 and 3

Office B houses project 4,5

User X works on project 1, which resides physically in office A and uses the Vault for project 1. Because the project is housed in Office A the user must connect to the Devolutions Gateway in Office A. All is fine up until now because what is preventing the user from making records that can make connections to projects 2 and 3?

Our firewall doesn't know which users makes which connection and I don't want to make a gateway for each project because that would create a massive overhead on our systems and management.

It seems to me that there needs to be a security mechanism in place which can limit a user to specific subnets he can connect to.

Hello,

We have Entra ID users in Devolutions Hub Business and would also like to auto-assign licenses. I have to assign every user a license after they activated their Devolutions account. In our case it's an RDM license and a gateway license and this causes unneccesary slowdowns.

Hello,

Gateway farms are currently being worked on; they are expected with 2025.1, which is targeted for January/February.

As for workarounds, it's probably technically possible, but it's not something that we have supported or tried before.

Have a good day!

Can't wait! Thanks.

Hello,

Thank you for reaching out to us with your request. We understand your concern, especially considering the security baselines and standardization requirements in enterprise environments.

I created an internal ticket for your request. I believe RPM packages may need to accommodate the target distribution, so we’ll start by targeting RHEL, and see if that works for Rocky Linux as well.

We’ll very likely _not guarantee_ support for distributions such as SUSE initially.

I’ll let you know when there is an update regarding this matter.

If you have any further questions or need assistance, feel free to reach out.

Best regards,

Hello, RHEL is just fine because Rocky is derived from this distro :)

Hello,

We would like to use Devolutions Gateway on RHEL/Rocky Linux instead of Windows and Ubuntu.

This is mainly due to the fact that Windows licenses are expensive for just a gateway and Ubuntu is no the OS I would use for enterprise production.

RHEL and Rocky include some security baseliens which we are standardising with but there is no RPM release of Devolutions Gateway available. I already did a build from source which seems to work but this isn't a production solution, I was really hoping that Devolutions will also include a RPM release besides the deb releases that are already ongoing.

This is something we actually need, how's the progress on this? In the meantime are there viable alternatives like a reverse proxy with loadbalancer in front of two gateway's?