The driver supports the following authentication methods:
  • No Authentication is used for REST services that do not require authentication. This is often used for publicly available data, such as services for weather or earthquake data, governmental census or statistcal data, or internal lists of lookup codes.
  • Basic Authentication authenticates using the specified user IDs, passwords, and HTTP headers.
  • AWS Authentication authenticates using AWS (Amazon Web Services) credentials.
  • Bearer Token Authentication authenticates an API Token, configured as BearerToken.
  • Digest Authentication negotiates user ID and password authentication using digest access authentication.
  • HTTP Header Authentication passes security tokens via the HTTP headers to authenticate. In some scenarios, the REST services may also authenticate the user ID.
  • URL Parameter Authentication authenticates by passing security tokens using URLs. In some scenarios, the REST services may also authenticate the user ID.
  • OAuth 2.0 Authentication authenticates using OAuth 2.0 authentication flows.
  • Custom Authentication authenticates using a series of requests defined in the Model file.

By default, the driver is configured to use no authentication (AuthenticationMethod=None).