Duaer

Integrations

Set up ServiceNow credentials in Duaer

Store ServiceNow connection details in Duaer for digital-organization nodes to use at runtime. Secrets are protected by the instance encryption key and are not written into node parameters.

Choose a ServiceNow credential type

The Duaer ServiceNow node supports two credentials:

  • ServiceNow Basic Auth API: put an account with REST API access and read or write roles on the relevant tables in User and Password. Subdomain comes from the instance URL: for https://dev99890.service-now.com, use dev99890.
  • ServiceNow OAuth2 API: in ServiceNow, open System OAuth > Application Registry and create an OAuth API endpoint for external clients. Set Redirect URL to the Duaer OAuth Redirect URL, put Client ID and Client Secret in the credential, fill in Subdomain the same way, then click Connect my account.

ServiceNow OAuth2 API

In Duaer, choose ServiceNow OAuth2 API when you create a credential, then fill in these fields:

  • Client ID (required)
  • Client Secret (required, secret)
  • Subdomain (required): The subdomain can be extracted from the URL. If the URL is: https://dev99890.service-now.com the subdomain is dev99890.

Duaer uses the OAuth2 Authorization Code grant for this type.

In the provider’s app settings, register the OAuth Redirect URL that the Duaer credential dialog shows (https://<your-duaer-host>/rest/oauth2-credential/callback). Then click Connect my account in Duaer and approve access.

By default, Duaer requests these scopes: useraccount.

Optional settings shared by every Duaer OAuth2 credential: Ignore SSL Issues (Insecure), Token Expired Status Code, Encrypted Tokens (JWE), JWKS URI. They are described under OAuth2 API.

Duaer nodes that use it: ServiceNow.

ServiceNow Basic Auth API

In Duaer, choose ServiceNow Basic Auth API when you create a credential, then fill in these fields:

  • User (required)
  • Password (required, secret)
  • Subdomain (required): The subdomain can be extracted from the URL. If the URL is: https://dev99890.service-now.com the subdomain is dev99890.

When you save, Duaer tests the connection with these values.

Duaer nodes that use it: ServiceNow.

Save the connection in Duaer

Open Credentials and create ServiceNow. Fill in the key, OAuth, or server fields. After you save, digital-organization nodes reference this credential instead of putting the secret in a parameter.

Credential values are protected by the instance encryption key. If you change or lose that key, stored credentials cannot be decrypted. See the hosting notes on encryption keys. The matching node is under the related node.

Who can use this credential

Who can see or edit it follows projects and roles. Do not paste secrets into chat or variables. External vaults are covered under external secrets.

Questions

Do ServiceNow secret values appear in Duaer node parameters?

No. In Duaer, ServiceNow secrets stay in the credential. Nodes only reference the credential. Execution records should not show the plaintext secret either.

What usually stops a ServiceNow credential from saving in Duaer?

Wrong fields, an OAuth callback that does not match the instance URL, or a role that cannot create credentials. Check the fields ServiceNow expects, then confirm you can create credentials in that project.

In this section