Authentication Issues with GeoSLAM Connect
Overview
This article explains how to login to Connect when you see the "My GeoSLAM login failed. Authentication failed! My GeoSLAM user doesn't belong to the same My GeoSLAM Account as this instance of GeoSLAM Connect" error.
Procedure
This error occurs when a user is trying to log in to Connect, and that installation of Connect has previously been logged into by a user from a different organization. This is a security feature of Connect. To log in, you have a few options:
- Log in using the user account that was used originally (if known)
- To fix the issue follow the below steps to allow you to log-in:
- Close Connect Viewer.
- Stop the connect service:
- Windows key; type "services" and open the "Services" App.
- Find "Connect".
- Right click and "Stop".
- Open a command prompt.
- Windows key; type "cmd" hit enter.
- Paste and run the command below (it's all one line).
"c:\Program Files\GeoSLAM Connect\bin\mongo.exe" --eval "db=connect('localhost/lidarDb');db.getCollection('LidarOSConfig').updateOne({idx:1},{$set: {magicDoorPrimaryAccountId:''}})" Expected output
...<several lines ending as follows>...
MongoDB server version: 4.2.0
{ "acknowledged" : true, "matchedCount" : 1, "modifiedCount" : 1 } - Restart Connect Service.
- Open Viewer and login with the correct My GeoSLAM account.
- If you are unable to perform the above, log in using the "Legacy local user" option. This will give you access to the functionality of Connect. However, if you forget the login details, you will not be able to recover them and will have to reinstall Connect to log in again.
- Last option would be to uninstall and reinstall Connect - you may lose your processing history and any custom geoscripts
Contact GeoSLAM support if none of these options are feasible.