anchor.diff:  </dependency>
   ----
   
  -NOTE: Developers wishing to contribute to the component are instructed
  +[NOTE]
  +====
  +Developers wishing to contribute to the component are instructed
   to look at the https://github.com/apache/camel/tree/master/components/camel-salesforce/camel-salesforce-component/README.md[README.md] file on instructions on how to get started and
   setup your environment for running integration tests.
  +====
   
   == Authenticating to Salesforce
   
  
positive.code: generated in previous request can be used in subsequent request. Individual requests and responses are linked with the
  provided _reference_.
  
  NOTE: Composite API supports only JSON payloads.
  
  NOTE: As with the batch API the results can vary from API to API so the result of the request is given as a
  `java.lang.Object`. In most cases the result will be a `java.util.Map` with string keys and values or other
  `java.util.Map` as value. Requests made in JSON format hold some type information (i.e. it is known what values are
  strings and what values are numbers), so in general those will be more type friendly.
  
  Lets look at an example:
  
  
negative.code: The component auto determines what flow you're trying to configure, to
  be remove ambiguity set the `authenticationType` property.
  
  [NOTE]
  ====
  Using Username-Password Flow in production is not encouraged.
  ====
  
  [NOTE]
  ====
  The certificate used in JWT Bearer Token Flow can be a selfsigned 
  certificate. The KeyStore holding the certificate and the private key
  must contain only single certificate-private key entry.
  ====
  
  == URI format
  
  