Originally posted by Stefano Bucco
Hi, ever since service m8 implemented 2fa we have not been able to use the private http authentication, the console log requires 2fa. but there is no documentation for handle this.
Please help
Hi Stefano!
Your observation is correct. When you enable Two-Factor Authentication (2FA) for an account, the standard private HTTP authentication methods will not work as before. This is by design to enhance security.
If you’re looking to make API calls or perform other automated tasks, you’ll need to switch over to OAuth authentication, which is built to support 2FA-enabled accounts. OAuth is a more secure and versatile authentication method that works seamlessly with 2FA.
Best regards,
Cody
For Implementing Oauth, it’s redirected to Authorize URL on browser. but our source code is running on backend side.
Is there any way to get a token on backend side ?
Once you have completed the oAuth 2.0 flow, where the user grants access to the account, you will be given a token which your backend servers can use to authenticate to the account.
Cody
Our source code is not for running in a browser, for an API. This API is used to automatically add new leads to SERVICE M8 when leads are created on another platform. Which means browser is not used. In such cases, it is difficult to obtain a token through OAuth. I am wondering if there any option to solve this issue during keeping 2FA on my account.