Switching data sources: navigation pane empty
In the AWS RDS database we have around 1500 entries.
The Azure SQL database holds 7200 entries.
Switching data sources: navigation pane empty
No luck, the read-only setting did not solve it.
I'll send you a private message with our contact details if you want to do a remote session.
Switching data sources: navigation pane empty
Both integrated security with AD, to 2 different domains.
One is using just AD, the other is using AD + MFA but MFA is 'skipped' (client IP in allow list).
Switching data sources: navigation pane empty
Version: don't know by heart anymore, I think maybe 2022.1.26 or the likes?
System settings > Cache/Offline: offline mode is set to "cache only"
User settings: offline mode is set to "cache only"
Caching mode for both data sources: "Intelligent"
View permission is set to "never" on 1 of the data sources, the other I have to check (I'm not an admin of that one)
I just checked with my own user settings, and for my (admin) user on the 1st data source the offline mode is set to "read-only".
Switching data sources: navigation pane empty
"reset layout" does not solve the issue unfortunately.
Users experiencing the problem are indeed not administrators of any of the data sources.
Switching data sources: navigation pane empty
Hi
We are using 2 data sources in RDM, 1 Azure SQL and 1 AWS RDS SQL. Since the update to 2022.2.17.0, a few of our colleagues are experiencing issues when they change data source in the navigation pane (using the dropdown). When they switch, the switch happens, but the navigation pane remains empty for the 'new' data source.
When they do a hard refresh (ctrl-f5), items do appear. When they switch back to the first data source, the issue re-occurs but now for the first data source.
Deleting the local cache file for both data sources for these users does not help.
Yesterday we updated to 2022.2.20.0, but that also doesn't help.
Weird thing is this only occurs for a few people, not everyone (let's say 5 out of 20 people).
Any other things these users could try to fix this?
Thanks!
FortiGate login screen and "m" key presses
Hi,
Unfortunately this also doesn't resolve our issue. RDM was completely restarted (including Windows logout/login) before testing.
Current configuration:
FortiGate session with Edge as web session browser
Wait Progress Mode set to "Status bar"
Best regards,
Frederic
FortiGate login screen and "m" key presses
Hi Gabriel,
I tested this out but unfortunately the issue is not resolved with the "Wait progress mode" adjustment. I also tried restarting RDM completely after changing the option, but still the same issue.
Best regards,
Frederic
FortiGate login screen and "m" key presses
Hi Gabriel,
I just upgraded one of our jumphosts to 2021.2.23.0, but the issue persists. Same behaviour as in the recording I sent previously.
Best regards,
Frederic
FortiGate login screen and "m" key presses
Thanks for the link, the recording has been uploaded.
FortiGate login screen and "m" key presses
Hi,
We have a small annoying problem with FortiGate login screens and RDM. When an existing web session (Chrome) to a FortiGate times out (on FortiGate side) and returns to the login screen, any subsequent "m" keypresses in any other RDM session always trigger a 'jump' to the FortiGate session. The "m" is not recorded in the original session where it was entered.
Steps to reproduce:
Open web session to FortiGate
Login to FortiGate
Open SSH session to some other device
Wait for FortiGate to time out and return to login screen
Press "m" in other SSH session
The solution: close the FortiGate web session in RDM. Re-opening the session and keeping it at the login screen does NOT trigger the issue!
We do not see this issue with other web-based login screens. We only see this issue with "m", no other key triggers this issue.
We have had this issue for a very long time (almost 2 years), and still have on our current version 2021.1.44.0
I'm personally working with an azerty layout, but as far as I know other people with qwerty layout encountered the issue as well.
I can provide a screen capture through private message if desired.
Open (select credentials) via jumphost not working
Hi Etienne,
Thanks, looking forward to engineering's findings :)
Frederic
Open (select credentials) via jumphost not working
Hi,
This is a follow-up to my previous thread User Specific Settings not used (SSH user/pwd and private key) (devolutions.net), where an upgrade of both my 'central' RDM application and the RDM application on the jumphost to 2021.1.44.0 solved the issue of connections not using user-specific settings.
I'm now running into a similar problem using the "Open (select credentials)" feature. So summarized:
SSH session configured with IP and jumphost session, credentials left to "none" or "custom"
User-specific settings with my personal private key credentials (from personal vault) on SSH session
When I open the session normally, the jumphost session launches, RDM gets started within the jumphost, and I'm logged in with my personal credentials. All fine and well.
However, I have a second set of private key credentials, which give me elevated access to the host in question. So I right-click the session, select "Open (select credentials)", pick my elevated account and try to log in that way. The result: RDM on the jumphost opens a second SSH session, but logs me in with my normal user.
If I change the user-specific credentials on the session to my elevated credentials, RDM keeps logging me in with my normal user.
Only when I completely close RDM on the jumphost, change the user-specific settings on the session, and relaunch the session (and thus RDM on the jumphost), then I can login with my elevated account. Ofcourse, now I cannot do a login with my normal account until I repeat this process :)
In the Connections.log file on the jumphost I do see a line like this when I select explicit credentials:
[9-9-2021 10:38:30] Information - 'private key entry name': Used by 'session name' [Session] (Private)
I tried playing around a bit with cache settings and clearing, but found nothing so far. Any insight?
User Specific Settings not used (SSH user/pwd and private key)
Hi Gabriel,
I forgot to mention we were using these sessions through RDM Agent on a few jumphosts, and didn't think about this during my troubleshooting. While updating RDM, I realized that RDM on the jumphosts was still a 2020.x version, which had to be upgraded as well.
Now that we're running 2021.1.44.0 on all servers, the issue has disappeared.
User Specific Settings not used (SSH user/pwd and private key)
I'm running into an annoying problem with user specific settings on a lot of my SSH sessions.
How the sessions are set up:
SSH session in some folder
Credentials on SSH session left to "Custom" or "None" - doesn't matter, I want everyone to log in with their personal account
Personal credentials (username/password or username/private key) in personal vault
User specific settings on SSH session overriding credentials, linking to my personal credential entry in my personal vault
When creating a new session this way, this works perfectly fine. I open a session, RDM uses my personal credentials automatically and I'm logged in.
However, after some time, a number of my frequently used SSH sessions stop 'using' the personal credentials. This manifests itself in 2 ways:
SSH sessions with username/password credentials linked just immediately ask for username password through popups - copy/pasting the credentials from my personal entry just works here, so it's not the credentials itself (more on that later)
SSH sessions with private key prompt immediately for a username, but when that username is provided, I'm also logged in - so the private key from the linked personal entry is still used!
So far I found only 1 solution: delete the SSH session completely, and recreate it from scratch as described above (the personal credential entries are not modified during this process!). After that, it works again for some time.
Given the number of SSH sessions we have documented, this solution is not usable in practice.
I'm suspecting some caching or local app data issue, but removing cache folders from the local appdata directory did not resolve this.
We are currently using 2021.1.36.0 and should probably upgrade, but the release notes from this version onwards do not mention any issues relevant to our problem.
Is this some known issue? With a known workaround/solution hopefully? :)
Edit: forgot to mention, but "Open with parameters" > "Open (select credentials)" just experiences the same problem: popups for username/password, popup for username where private key is used but private key is then automatically sent from the personal credential entry
Tag propagation (or other tag search tricks)
Hi,
We are trying to use tags to attach information to certain content in RDM, things like customer or application names. Since we use a folder structure to organize our entries, we want to add tags to a certain level in this folder structure and then have the tags propagate down to all entries below that folder.
It looks like RDM is not doing this (by default?). How can we use tags efficiently to search for information based on 'meta' data?
Is there a way to have changes to tags propagate down to subfolders and entries in those folders? E.g. we add or change a tag on a folder -> all entries below that folder automatically get applied the new/changed tags
Is there a way to search for a tag only applied on a top-level folder, but have RDM also show the entire content of that folder?
Thanks!