Skip to main content

SERVICENOW_CONNECTOR_UNAUTHORIZED_ACCESS_ERROR error condition

SQLSTATE: KD000

An error occurred in ServiceNow. Source API type: <saasSourceApiType>.

MISSING_USERACCOUNT_AUTH_SCOPE

Authentication failed: Missing required 'useraccount' scope in OAuth configuration.

To resolve this, go to ServiceNow >> System OAuth >> Application Registry. Then select the OAuth client application used for the connection. Finally, ensure that the 'useraccount' scope is selected in the Auth scopes list.

If the error persists, file a ticket.

TABLE_ACCESS_INSUFFICIENT_RIGHTS

Fetching schema from source failed: Insufficient rights to access the schema of the table '<tableName>'. The current user does not have the required privileges to access the schema.

To resolve this, assign it an admin role. (We recommend assigning it the snc_read_only role, too.)

If the error persists, file a ticket.

UNAUTHORIZED_ACCESS_ON_SYS_DICTIONARY

Failed to fetch the list of all tables: Insufficient permissions to access the table 'sys_dictionary'. The current user does not have the required privileges for this table.

To resolve this, grant this user read permissions to the table in ServiceNow >> System Security >> Access Control, or assign it an admin role. (We recommend assigning it the snc_read_only role, too.)

If the error persists, file a ticket.

UNAUTHORIZED_SCHEMA_ACCESS

Fetching schema from source failed: Insufficient permissions to access the schema of the table '<tableName>'. The current user does not have the required privileges to access the schema.

To resolve this, assign it an admin role. (We recommend assigning it the snc_read_only role, too.)

If the error persists, file a ticket.

UNAUTHORIZED_TABLE_ACCESS

Authentication failed: Insufficient permissions to access table '<tableName>'. The current user does not have the required access privileges for this table.

To resolve this, grant this user read permissions to the table in ServiceNow >> System Security >> Access Control, or assign it an admin role. (We recommend assigning it the snc_read_only role, too.)

If the error persists, file a ticket.