Connections And Credentials

Ansible Tower credentials are required to access your Ansible configuration management account. Use these credentials to manage Ansible resources through the Cloud Management application.

An API key is a unique code that is passed in to an API to identify the calling application or user.

Some applications require credentials in addition to the credentials the that host machine requires. Credentials required to access these applications are referred to as applicative credentials.

Verify the identity of the sender using Authentication Algorithms

Credential alias gives an administrator more control over the credentials used in Orchestration activities.

Credential affinity is an association between a set of credentials and a device on your network.

The MID Server integration with the CyberArk vault enables ServiceNow Orchestration, ServiceNow Discovery, and ServiceNow Service Mapping to run without storing any credentials on the instance.

These procedures include both CyberArk and ServiceNow configuration tasks, including references to the appropriate CyberArk documentation.

An instance can store credentials used by Discovery, Orchestration, and Service Mapping in an external credential repository rather than directly in a ServiceNow credentials record.

Discovery explores many kinds of devices (switches, routers, printers, and so on) using the SNMP protocol. Credentials for SNMP don’t include a user name, just a password, called the community string.

Chef server credentials access chef integrations with the instance.

Generate the custom data needed to authenticate to a web service by running script.

Generate the Amazon Signature based data needed to authenticate to a web service by running script.

Configure a JAR file and credential identifiers so that the JAR file resolves the credential identifiers into actual credentials from the CyberArk external vault. The process enables the MID Server to get and include OAuth 2.0 credentials in the OAuth token request.

Configure an authentication algorithm so that you can sign outbound HTTP requests.

Configure your system to use Java Messaging Service (JMS) with a custom JMS activity or action.

Configure the CyberArk vault to store OAuth 2.0 credentials and respond to requests for OAuth 2.0 credentials from the MID Server.

Configure a connection to send requests for OAuth 2.0 tokens to a third-party auth server via the MID Server. The MID Server adds OAuth 2.0 credentials (Client ID and Client Secret) from the CyberArk external vault, OAuth scope, and token URL from the instance to the request and sends them to the third-party auth server.

Configure your CyberArk vault with OAuth 2.0 credentials that the ServiceNow instance requests.

Configure connection information to use with a custom activity or action that uses the PowerShell or Secure Shell (SSH) protocol.

Define an alias to label a credential or connection record.

Use the connections table to set up a Basic, JMS, JDBC, or HTTP(s) connection to a target host.

The container image repository credentials manage access to private repositories for container image scanning. This credential type is available for Discovery.

Create a connection record that enables the sending of an OAuth token request to a third-party server via a MID Server.

Define connection-specific variables that you can use in Integration Hub integration steps.

Configure your CyberArk vault with the AWS credentials to be retrieved for use by your instance.

Configure your CyberArk vault with the Azure credentials to be retrieved for use by your instance.

The HTTP(s) connection provides the information custom HTTP(s) actions or activities use to connect.

The JDBC Connection provides the information custom JDBC actions or activities use to connect to various target databases.

Create a template that defines the inputs required to set up a spoke. Set static key-value pairs to create records and set values that apply to every integration. Set dynamic key-value pairs to gather user input and set field values that may vary. Using this template, admins and flow designers can set up the spoke from a single form.

All application integrations in the ServiceNow AI Platform use connections, credentials, and aliases to enable applications to access resources.

The MID Server uses the credentials you create in the Credentials [discovery_credentials] table to access resources for Discovery, Orchestration, Service Mapping, and Cloud Management.

Credential aliases for Discovery allow an administrator to use specific credentials on Discovery schedules. You can configure behaviors for your aliases that determine how strictly the system enforces their use.

This example configuration template sets up Credential and Connection records using the JWT Bearer grant type to authenticate requests to Docusign.

Domain separation is supported in Credentials and Connections. Domain separation enables you to separate data, processes, and administrative tasks into logical groupings called domains. You can control several aspects of this separation, including which users can see and access data.

Configure your instance to obtain credentials from a remote repository.

Infoblox credentials are required to set up IP pools (IPAM) in the Cloud Management application.

Store OAuth 2.0 credentials-client ID and client secret-in the CyberArk vault instead of the ServiceNow instance. The MID Server gets the credentials from the CyberArk vault, when required to get the OAuth token. The token is stored in the MID Server and refreshed automatically upon expiry.

OAuth 2.0 credentials enable ServiceNow to obtain access to user accounts on an HTTP service.

The basic authentication credential type manages access to store basic authentication credentials.

The CIM credential type manages access to a CIM server (also referred to as a CIMOM - Common Information Model Object Manager) for information about VMware ESX servers. This credential type is available for Discovery.

Cloud credential types manage access to cloud-based applications, including Amazon Web Services and the Microsoft Azure cloud.

Review the <credentials_debug> section of the ECC queue payload to troubleshoot issues with credentials.

The JDBC credential type manages access to a Java Database Connectivity (JDBC) connection. This credential type is available for Discovery and Orchestration.

The JMS credentials type manages access to a Java Message Service (JMS). This credential type is available for Discovery and Orchestration.

The SAP credential type manages access to SAP JCo systems. This credential type is available for Discovery and Orchestration.

Discovery, Orchestration, and Integration Hub explore UNIX and Linux devices by using SSH credentials to execute commands over Secure Shell (SSH). SSH commands must run with root privileges, either with root credentials or through the use of sudo. SSH private key credentials provide additional security.

The VMware credentials type manages access to vCenter credentials.

Windows credentials provide access to Windows computers. This credential type is available for Discovery and Orchestration.

Credentials and connection information are required to gain access to a computer or network device for Discovery, Service Mapping, and Cloud Management or to perform work using Orchestration. When adding content to Share or AppStore, you can configure connections and credentials relevant to your environment without modifying built content.

You can classify certain types of Connection & Credential records as belonging to a scope, and extend scope protections to them. These scope policies protect records you create in a table, and prevent interactions with records that are private to another scope.

Enable users with the admin and flow_designer roles to set up spoke integrations with third-party systems using a single, customizable form.

The External Credential Storage plugin is available by request.

You can check the IP Services table for a list of IP addresses that are associated with a protocol.

Create the unique key that CyberArk can use to identify specific credentials in the external repository.

If your system uses SNMPv2, you can create a special file to map the attribute in a credential to the community string.

Configure the config.xml file to grant the MID Server access to the CyberArk vault with AIM API.

Configure the config.xml file to grant the MID Server access to the CyberArk CCP vault.

Create and test the credentials that Discovery, Service Mapping, Cloud Management, and Orchestration require to access hardware and software in your network.

Import the CyberArk JavaPasswordSDK.jar file into the instance to make it accessible to the MID Server.

Configure the CyberArk vault to allow MID Server access and install the CyberArk AIM API on the MID Server machine.