Can a Windows account be used with the REST API if the gateway is not using SSO authentication?

The answer is Yes. The User Authentication section in the Gateway Commands Reference Guide states:

"If the gateway is configured with authentication enabled, then all REST command requests must come with user credentials that the gateway can verify.

The REST service supports two types of user credentials. SSO tokens can be used to authenticate SSO users. User name and password can be used to authenticate users who have passwords configured in the gateway setup.

System logins are not supported, since system credentials are checked by the user interface client (e.g. Active Console), which is not involved in the REST API. However, it is possible to use System login for Active Console users while using password-based authentication for the REST API."

In the Gateway Setup Edit:

- go to the Windows account and add a user defined password

- and make sure the user has the permission to execute the command (map the user to a role with the permission)

Below is an example of a Windows Test User mapped to a role with permission to run all commands except manually snooze: