Authentication Guide

In the Authentication Guide, you'll find information about password requirements and policies in NetSuite. NetSuite supports several authentication methods, including two-factor authentication, token-based authentication, OAuth 2.0, Device ID authentication, Single Sign-on, Digital Signing, SSH Keys, and RESTlet authentication.

Overview

Learn general information about password requirements, session management, login pages, and setting IP address rules for your account. For more information, see Authentication Overview.

Two-Factor Authentication (2FA)

Two-factor authentication adds another layer of security when logging in to NetSuite and helps protect your company from unauthorized access. For more information, see Two-Factor Authentication (2FA).

Token-based Authentication (TBA)

Token-based authentication boosts security and lets client applications use a token to access NetSuite through APIs, so you don't need to store user credentials. For more information, see Token-based Authentication (TBA).

OAuth 2.0

OAuth 2.0 lets client applications use a token to access NetSuite through REST web services and RESTlets. For more information, see OAuth 2.0.

Device ID Authentication

Device ID authentication lets account administrators restrict logins to only approved devices registered in NetSuite. For more information, see Device ID Authentication.

Single Sign-On

Single Sign-On lets you to log in with a single ID and password. NetSuite supports SAML Single Sign-on, and OpenID Connect (OIDC) Single Sign-on.

Digital Signing

Digital Signing authenticates documents or messages so that you can trust the sender and the document contents. For more information, see Digital Signing.

SSH Keys for SFTP

Use SSH keys to set up an SFTP connection and manage files and directories with the SSH file transfer (SFTP) protocol. For more information, see SSH Keys for SFTP.

RESTlet authentication

RESTlets require authentication and process calls synchronously. Learn more about RESTlet authentication, setting up token-based authentication and OAuth 2.0 for a RESTlet integrations, and using user credentials. For more information, see RESTlet Authentication.

Related Topics

General Notices