The following login methods are available for OAuth configuration:

• Windows
• Oauth
• OAuth – Service to Service
• Oauth – User Impersonation

Windows

• Used for Web Service Access Key (WSAK) authentication in SaaS (until deprecated) and for navserver password in on-premise installs
• Standard Warehouse Insight prompt for scanning/entering Windows credentials.
• Supports the Windows Login Badge report in Business Central for easier sign on.

OAuth

• Uses the authorization_code grant type
• Embedded login form (the same as Warehouse Insight 2.7)
• Supports multi-factor authentication (MFA)
• Most secure and supported option
• Enabled by default
• Does not respond to barcode and badge scanning

OAuth – Service to Service

• Uses the client_credentials grant type
• Does not use/care about multi-factor authentication (MFA)
• No login prompt
• Likely needs to be used in conjunction with Insight Works Users
• Business Central access is run under a fictitious user account named after the Description field value in the Azure Active Directory Application entry in Business Central (name appears as the user logged into the scanner if Insight Works Users are not used).
• Permissions are based on the Azure Active Directory Application entry in Business Central
• Users must fill in additional information for the application registration:
  • Client ID
  • Tenant ID
  • Client Secret

For more information, see Azure Active Directory (AAD) OAuth Configuration for Warehouse Insight 2.8+.

OAuth – User Impersonation

• Uses the password grant type
• Presents the user with a login prompt to enter username and password
• Supports the Windows Login Badge report in Business Central for easier sign on

• Cannot use an account that uses multi-factor authentication (MFA)
• Result is similar as OAuth login method and allows for scanning a badge but is considered less secure
• Users must fill in additional information concerning the application registration:
  • Client ID
  • Tenant ID
  • Client Secret