58 views

Description

From Jakarta, if the 'Explicit Roles' plugin is installed,  ODBC connection from users with snc_external is not allowed.

Testing using the Interactive SQL (iSQL), it returns a 403 forbidden error.

The same user can login directly using the browser and access the tables without problems. SOAP calls will also work.

404 error

Steps to Reproduce

  1. On a Jakarta instance create a user called 'odbc_user'.
  2. Grant the user the 'odbc' role. This will include 'soap_query' and 'itil' roles.
  3. Now activate the 'Explicit Roles' plugin.
  4. Go back to the user and remove the 'snc_internal' role and grant the 'snc_external' role.
  5. Now setup an ODBC connection to ServiceNow.
  6. Using ISQL, try to connect with the odbc user from item 2 above.

    A 403 Forbidden error is returned

Workaround

This problem is under investigation. As a workaround, give the user the 'snc_internal' role. Alternatively, disable the 'explicit role' feature.

 


Related Problem: PRB1237871

Seen In

There is no data to report.

Intended Fix Version

ODBC 1.0.15

Safe Harbor Statement

This "Intended Fix Version" information is meant to outline ServiceNow's general product direction and should not be relied upon in making a purchasing decision. The information provided here is for information purposes only and may not be incorporated into any contract. It is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. The development, release, and timing of any features or functionality described for our products remains at ServiceNow's sole discretion.

Associated Community Threads

There is no data to report.

Article Information

Last Updated:2018-05-01 08:58:35
Published:2018-02-21