Signing into Expensify and NetSuite: All about 2FA, SSO, and Token Based Authentication
Now that NetSuite requires admins to sign in with two-factor authentication (2FA), a lot of people have been wondering if that impacts the Expensify integration. Good news: it doesn’t. You can keep using Expensify with NetSuite’s 2FA requirement!
Nonetheless, we decided to implement an additional way to sign into Expensify to give you even more options. It’s called Token Based Authentication, but we’ll spare you the jargon. The main thing to know is that this is another option for connecting Expensify to NetSuite, which will also work well with NetSuite’s latest updates. If you’d like to make the switch, check out this step-by-step guide to enable Token Based Authentication for your company.
Integrations that are affected by NetSuite’s new 2FA requirement are those that are using inbound SSO and the mapSSO API. Expensify uses a manual mapping method with inbound SSO, so enabling 2FA doesn’t break that mapping.
However, we did a bit of SSOul searching and realized that Token Based Authentication, which is based on roles instead of users, is a much simpler and more secure way to connect since it utilizes a dedicated Token ID and Token secret rather than user credentials.