(user deleted)
Add SAML or OIDC support
Thank you!
If you need help with a beta test, I'm available. Let me know
Add SAML or OIDC support
Hello,
is there any news about generic OIDC (or at least Okta) support in DVLS?
Thanks
Add SAML or OIDC support
To be honest I'm a little bit disappointed. We waited that feature for a long time and it was postponed many times. OIDC is a standard and limit it to a single vendor is not what we expect when we think about SSO.
Moreover why start with AzureAD since you have already an integration for Office365?
I hope that you think about release OIDC as customizable, in order to use it with any IdP.
Thanks
Add SAML or OIDC support
Hello Maurice,
I'm writing just to ask if there is any news about the support for OIDC or SAML in DVLS
Thanks
Add SAML or OIDC support
We have been authorized to start on OpenID, it is planned for the 2021.3 release.
This is a great news!
Just for confirmation, the OIDC login flow will be supported also on RDM?
If you are open to beta test that feature I'm available.
Thanks
RADIUS and IP address of user
Hello,
I'm trying to use a RADIUS server for MFA.
I've found that the real IP address of the user that is trying to login is not passed in the RADIUS request.
This is not fine because we cannot identify the source network of the user and then apply the right MFA policy. Moreover in our log the request will be recorded as arriving from the Devolutions server instead from the user's ISP.
Is there a way to add the source IP of the user in RADIUS request?
Usually in RADIUS a special attribute ID is used in request to pass the real-ip of the user. For example:
Cisco, Juniper, Citrix and F5 use "31 Calling Station ID" (that is also the RADIUS standard for this purpose). Palo Alto Networks use "26 PAN Vendor ID".
Do you think is something that you can implement in next releases?
Add Okta and to 2-Factor Authentication
I add my upvote for Okta support.
Or you can just add support for SAML or OIDC federation, then we can easily integrate with Okta.
RADIUS has some leak and it's not the best solution for integrate the Okta MFA features.
SAML Authentication
my upvote for SAML or OIDC support. Any news about this topic?
Add SAML or OIDC support
Years passes and despite various promises in past, I see that there isn't yet a support for login using a SAML or OIDC federation.
We are in 2021, and SSO protocols are very popular and it's amazing that software like RDM / Devolutions still doesn't support them.
Do you have any indication on this? is on the roadmap?
SAML or OIDC support for login and MFA
Years passes and despite various promises in past, I see that there isn't yet a support for login using a SAML or OIDC federation.
We are in 2021, and SSO protocols are very popular and it's amazing that software like RDM / Devolutions still doesn't support them.
Do you have any indication on this? is on the roadmap?
Rename or Allow Customization of "RADIUS Code" Text
Upvote for make the RADIUS request string customizable.
This will be able us to add important information about the custom MFA process in our RADIUS server.
Do you think that is something you can evaluate for next releases?
After update to 2019.1.34.0 users can't access
Same problem here, hoping to have a quick fix ;)
After upgrading to v. 13 some SSH sessions are not working
Hello David,
With the default client is working fine, but we need to solve also with Rebex for two reason:
1) with the default client some function key are not working fine
2) we cannot easily convert sub connections
and 3)... if it was working before update I expect that will work again. Convert and tests hundreds of sessions need time
Do you have plan for fix this issue in next release?
Thanks
Fabio Grasso
After upgrading to v. 13 some SSH sessions are not working
Hi David,
yes I'm using Rebex
Thanks
After upgrading to v. 13 some SSH sessions are not working
Hello,
I've just upgraded to v. 13 and now I have some of my SSH sessions that are not working fine.
When I try to connect I receive this error:
Negotiation Failed. Server signature is not valid.
I've tried to downgrade to v. 12 and they work fine.
Any suggestion?
Thanks
After upgrade from 4.5 to 4.6 can't login anymore (authentication error)
Hello Maurice,
I've a similar problem and I've found that most of my users have authentication type "Custom (Devolutions)" instead of "Domain".
I'm sure that before the upgrade they was using the AD password for login so I think that's this change was introduced after the upgrade.
I've sent to your support email some additional screenshot of my environment. It's very urgent for us to solve, I'm available for a remote session when you are available
Thanks