Skip to main content
Noxus reads and writes ServiceNow records, knowledge articles, tags and attachments. A ServiceNow connection points at one instance and offers two ways to sign in:

​
Connect with OAuth

Every ServiceNow instance is its own OAuth server, so you register an OAuth app on your instance once and enter its details in the connection. Registering the app needs the security_admin role on the instance.
1

Copy the redirect URL from Noxus

Open Connections in the sidebar, click Add connection, choose ServiceNow, then OAuth. Copy the Redirect URL at the top of the form and keep the form open.
2

Register an OAuth app on your instance

On Zurich and later releases, open System Security > Machine Identity Console, go to Inbound integrations, and create a new integration with the OAuth - Authorization code grant type. On earlier releases, open System OAuth > Application Registry and choose Create an OAuth API endpoint for external clients.Paste the redirect URL from Noxus into the app’s Redirect URL field and save. ServiceNow shows the app’s Client ID and Client Secret.Add the useraccount auth scope to the app. On an Application Registry record it is in the Auth Scopes related list. Newer releases do not add it by default, and without it every call fails with “Access to unscoped api is not allowed”.
3

Enter the app in Noxus and sign in

Back in the form, enter your Instance (for example acme.service-now.com; a full URL or just acme also works), the Client ID and the Client Secret, then click Continue with OAuth.Your instance’s login page opens. Sign in the way you normally do, including SSO or MFA, and allow access. You return to Connections with an Active connection. Its Metadata tab shows the instance, the client ID and the user who signed in. The client secret is never shown again.
Noxus refreshes the connection’s access token by itself, so workflows keep running. Everything they do is done as the user who signed in, with that user’s roles.

​
Reconnect or change the app

Open the connection and go to Credentials. Reconnect opens your instance’s login page again and keeps the instance and app you entered. To move to another app, or after rotating its secret, change the fields before you click Reconnect. Leave the client secret blank to keep the current one; it is only kept while the instance and client ID stay the same. A connection shows Needs reconnect if ServiceNow stops accepting its refresh token, for example once the OAuth app’s Refresh Token Lifespan (100 days by default) has passed. Raise that lifespan on your instance to make connections last longer.

​
When sign-in does not start

If ServiceNow shows an error after you sign in, check that the app’s redirect URL is exactly the one Noxus shows, and that the client ID and secret belong to the same app. If the connection shows Invalid with “missing the useraccount auth scope”, add that scope to the app and click Reconnect. A token keeps the scopes it was issued with, so the connection needs a new one.

​
Connect with a username and password

Choose Username and password instead of OAuth, and enter the instance, the username and the password of a ServiceNow user. Noxus checks them when you save. A refused password marks the connection Invalid with the reason.