MacOS Keeper SSO integration having problems.
We have MacOS on the network that use the RDM (paid lic. version) and we have recently deployed KEEPER Security on mine and one other. I originally had setup the vault to use "Enterprise SSO (Domain)" but started receiving errors early last week. I was able to resolve the isseu by changing my selection to just using "Enterprise SSO".
Since then, I was introducing it to my co-worker and she couldn't use either "Enterprise SSO (Domain)" or "Enterprise SSO" for KEEPER. The following is what error we were seeing when she did.
"An unexpected error has occurred. Please check the execution log."
Devolutions.RemoteDesktopManager.Business.TryGoOfflineException: Could not resolve host 'SNML-0PCML87.local' ---> System.Net.Sockets.SocketException: Could not resolve host 'SNML-0PCML87.local' at System.Net.Dns.Error_11001 (System.String hostName) [0x00015] in <381a4f5c7c4942ca9815982241f9fcae>:0 at System.Net.Dns.GetHostByName (System.String hostName) [0x00021] in <381a4f5c7c4942ca9815982241f9fcae>:0 at System.Net.Dns.GetHostEntry (System.String hostNameOrAddress) [0x00052] in <381a4f5c7c4942ca9815982241f9fcae>:0 at System.Net.Dns.GetHostAddresses (System.String hostNameOrAddress) [0x00056] in <381a4f5c7c4942ca9815982241f9fcae>:0 at System.Net.Dns.GetHostAddresses (System.String hostNameOrAddress) [0x00000] in <97c73ccdd4e04e6ea1d6850cff55d179>:0 at Client.KeeperResolvingViewController.GetDeviceInfo (Devolutions.RemoteDesktopManager.Business.Connection connection) [0x0001c] in <5618fb869c08493cb08fd58f19dc9fb7>:0 at Client.KeeperResolvingViewController+<>c__DisplayClass20_0.<LoadView>b__0 () [0x00099] in <5618fb869c08493cb08fd58f19dc9fb7>:0 --- End of inner exception stack trace ---
Can someone tell me why this happening or what the fix is.
I am on a older 2017 Mac whereas she is on a newer Mac.
All Comments (9)
Hi,
We are aware of some issues with Keeper on RDM Mac and
we are working on updating the session.
While I cannot guarantee this will solve the problem,
the errors you showed us tend to make me think it will be solved when we will push the changes.
We will try to push them as fast as we can but I can't give you an ETA.
Meanwhile I will try to keep you updated on it is advancing.
Best regards,
Michel Lambert
Thank you for the reply,
Its so werid we are running the same version of RDM (2023.3.9.3) on two different macs and get different outcomes.
Thanks again.
Hi,
As mentioned before, our newest version of RDM Mac (2023.3.10.2) fixed some issues we had with our Keeper session.
Since your issues looked a lot like the issues we had, we have good hopes that it might have solved your.
If it doesn't work or if there's anything else, don't hesitate to communicate with us.
Best regards,
Michel Lambert
STATUS UPDATE:
We have received and installed 2023.3.10.2 and tested.
The SNML-0PCML87.local MacBook is working now with Keeper.
thank you
Well, I spoke up too soon.
After a day of it working on the latest release the SNML-0PCML87.local MacBook stopped working with Keeper and RDM.
The day it was working she was working from the office.
The next day the employee was remote work from home and ran into the orginal error message when trying to access her vault. That was both tried on the VPN and off the VPN.
The only other difference is our MacOS versions. She is on the newest release Sonoma, while I am back one major version due to the age of my Mac.
Hers
SNML-0PCML87•macOS 14.1 (23B74)
Memory
16.00 GB
CPU
1 X Intel(R) Core(TM) i7-1068NG7 CPU @ 2.30GHz
Mine
MAC7DAHTDF•macOS 13.6.1 (22G313)
Memory
16.00 GB
CPU
1 X Intel(R) Core(TM) i7-7820HQ CPU @ 2.90GHz
Not sure if any of this helps.
Update to the information
The user having problems seems to be fine when she is on the network at work. It is only when she is off network or on the vpn that it has this issue. Seems to be a DNS issue either in RDM or on the MacOS.
Hi,
We'd need to have a confirmation of the issue being caused by the DNS resolving of the Mac, because if so, there's really not much we can do. If it's the case, and assuming the host accepts ping request, it should be easy to confirm when the issue occurs in RDM, the user can try to ping the host in question (we can see SNML-0PCML87.local in the previous logs) and if the ping fails, the issue is with the Mac.
Best regards,
Michel Lambert
Quick status update...
I have seemingly found a way to
1) show its a DNS issue
and
2) resolve the problem.
Last week I was reviewing the issue again with problem child mac user and decided to try modifying the MacOS "hosts" file found in the the /etc/ directory. I added the following assignment to the users hosts file. (Even though my macbook didn't seem to need this entry at all)
127.0.0.1 SNML-0PCML87.local
After testing on and off the network and on and off the VPN. The keeper plug-in in RDM seems to be working. The user was able to access her Keeper vault and utilize the creds in the vault for her Remote Desktop Manager
This seems to show that somewhere in her Mac, the RDM application has problems knowing the hostname of the machine in certain circumstances. Anyways, call it a fix or a work-around, I call it working successfully. :)
If you have questions, Feel free to reach back out. Hope this helps with your diagnosis of this issue.
Hi dkeller
Glad you could resolve your issue
Best regards,
Michel Lambert