Security and Authentication

To protect data from unauthorized access, ServiceNow data stores require connections to be authenticated with an access token or . Some data stores also require connections to be encrypted using the Secure Sockets Layer (SSL) protocol. The Simba ServiceNow ODBC Connector provides full support for these authentication protocols.

Note: In this documentation, "SSL" refers to both TLS (Transport Layer Security) and SSL (Secure Sockets Layer). The connector supports up to TLS 1.2. The SSL version used for the connection is the highest version that is supported by both the connector and the server.

The connector uses the OAuth 2.0 protocol for authentication and authorization. You can authenticate your connection through OAuth 2.0 by specifying your ServiceNow application information so that the connector retrieves and uses the corresponding access token.

Note: The access token has a Default value of 300 seconds. You can set a larger value in the Service Now Dashboard under Application Registry Tab.

The connector also supports basic user name and password authentication. You can authenticate your connection by providing your user name and password in the DSN or connection string.

Additionally, the connector supports SSL connections with or without one-way authentication. If the server has an SSL-enabled socket, then you can configure the connector to connect to it.

It is recommended that you enable SSL whenever you connect to a server that is configured to support it. SSL encryption protects data and credentials when they are transferred over the network, and provides stronger security than authentication alone.