Upcoming changes to authentication process

[cvigier]

Hi everyone!

We want to inform you of two important updates regarding our upcoming authentication migration:

• The migration start date has been extended to June 16^th, 2025.
• New URLs must be allow listed before this date to ensure a successful migration.

We apologize for any inconvenience this may cause and appreciate your attention to these changes.

Required: Add URLs to your allowlist

To avoid disruption, make sure the following URLs are accessible from your environment before June 16^th:

• https://ls.auth.lansweeper.com/ – This URL is used to enable the migration process.
• https://login.auth.lansweeper.com/ – New login URL.

If these URLs are not reachable, you will not be able to log in or start the migration. However, simply allowing these URLs will restore access.

Updated migration phases

• Phase 1 — Soft Migration Period: During this phase, both the old and new authentication providers will coexist, allowing organizations—particularly those using SSO—time to transition smoothly. This period will last from June 16^th until June 29^th.

• Phase 2 — Full Migration: In this phase, the old authentication provider will be fully disabled, and any remaining accounts will be migrated to the new provider. For organizations using SSO, this means access will be lost until the administrator updates the configuration with the new authentication provider. Phase 2 will last from June 30^th to July 3^rd.

What this means for you

As I mentioned, the level of impact and any actions required will depend on your specific role and your organization’s authentication setup. The different scenarios and necessary actions are summarized in the table below:

Authentication Type	User Role	Phase 1 (Jun 16th – Jun 29th)	Phase 2 (Jun 30th - Jul 3rd)
Email/Password	Local user	Credentials will be automatically migrated when logging in.	If not logged in during Phase 1, users must reset their password.
Social Login	All users	Users will need to grant access again to the application via their social login provider.	Users will need to grant access again to the application via their social login provider.
SSO (Single Sign-On)	Lansweeper user	Users can continue logging in using the old authentication provider.	Users cannot log in until the SSO admin completes the update of IdP connection parameters.
	SSO admin	Admins must trigger the connection migration from the UI and update parameters in the Identity Provider (IdP). For more information, see our migration guide.	The connection will be automatically migrated, but SSO login will be unavailable until IdP is updated. For more information, see our migration guide.
MFA (Multi-Factor Authentication)	Lansweeper user	MFA will be lost during migration. Users will need to reconfigure it on their secondary device.	MFA remains unavailable until users reconfigure it.

Next steps

We highly recommend logging in as soon as possible after Phase 1 begins to avoid disruptions during Phase 2.
If you're having trouble logging in, fill out the Contact Sales & Customer Service form, select “I have a question about the Support Portal”, and describe your issue.

Stay tuned for more updates, and thank you for your understanding as we work to enhance your security and login experience!

[JamesMalmsteen]

Some of our co-workers can't access now with their credentials, they had a local account, and even some saved passwords on their browsers. Now, all these accounts are not working with an "Invalid login credentials", but if they select the "forgot password" button, there is a "504" Error on the page

[removed]

Hello @JamesMalmsteen 

Please open a ticket through our support portal so our team can assist you further. We are currently working on resolving some authentication issues in relation to SSO/MFA, but if the problem persists, it may be specific to your site and will require individual attention.

[yp-tg]

Migration didnt start yet but there are issues with Google or MS login which worked before, now it looks like it creates a new user/account even tho the email is the same.
It seems to ignore the fact that I already used MFA.

[removed]

Hello @yp-tg 

Our tech support team should be able to assist you with this.  Please open a ticket in our support portal.

[yp-tg]

for me it resolved on it own.

even after migration.