Salesforce OAuth2 Login Exampleab129a1d-2ba7-42ce-8757-cd47fe4e114bf990f6a5-841c-4d59-8a0e-08744febdc62838.6338402732085498.331857150740605f530504-012c-491e-ba50-335435232a33ab129a1d-2ba7-42ce-8757-cd47fe4e114b0 MB0ab129a1d-2ba7-42ce-8757-cd47fe4e114bd1801cf3-ea7f-4b52-847f-5d2240629883PROCESSOR0 sec10a5bd7042-3fe7-4046-b10f-412a33a94b7eab129a1d-2ba7-42ce-8757-cd47fe4e114b0 MB0ab129a1d-2ba7-42ce-8757-cd47fe4e114bbcc1c5d5-8f6a-4e4e-adc0-5dcbee8985d6OUTPUT_PORT0 sec1matched0da158696-ae59-4579-996d-d7a14fac2e72ab129a1d-2ba7-42ce-8757-cd47fe4e114b0 MB0ab129a1d-2ba7-42ce-8757-cd47fe4e114b4eea2682-95d6-4dc2-9b43-0d58cc6114cdPROCESSOR0 sec1FailureNo RetryRetry0174fabe0-09b4-4087-a723-580256d9fedeab129a1d-2ba7-42ce-8757-cd47fe4e114b0 MB0ab129a1d-2ba7-42ce-8757-cd47fe4e114b628138c7-31f1-4b60-892f-50ccc46744d9PROCESSOR0 sec1success07182e9b2-0b32-4f5a-af6d-69b414ebea15ab129a1d-2ba7-42ce-8757-cd47fe4e114b0 MB0ab129a1d-2ba7-42ce-8757-cd47fe4e114b0face432-ec9c-4a39-802c-90b628fc19bcPROCESSOR0 sec1Response03a12d9ba-7d97-4877-b945-971c683c334eab129a1d-2ba7-42ce-8757-cd47fe4e114b54.4623565673828124.9736442565917971Login RequestSTOPPEDINPUT_PORTbcc1c5d5-8f6a-4e4e-adc0-5dcbee8985d6ab129a1d-2ba7-42ce-8757-cd47fe4e114b1572.6612548828125213.833190917968751Salesforce Oauth2 SessionIDSTOPPEDOUTPUT_PORT'Port 'Salesforce Oauth2 SessionID'' is invalid because Output connection for port 'Salesforce Oauth2 SessionID' is not defined.d1801cf3-ea7f-4b52-847f-5d2240629883ab129a1d-2ba7-42ce-8757-cd47fe4e114b469.9633499011104-3.77349687388903WARN1TIMER_DRIVEN1EVENT_DRIVEN0CRON_DRIVEN1TIMER_DRIVEN0 secCRON_DRIVEN* * * * * ?File to Fetch${absolute.path}/${filename}The fully-qualified filename of the file to fetch from the file systemFile to FetchfalseFile to FetchtruefalsetrueCompletion StrategyLeave the file as-isNoneNoneMoves the file to the directory specified by the <Move Destination Directory> propertyMove FileMove FileDeletes the original file from the file systemDelete FileDelete FileNoneSpecifies what to do with the original file on the file system once it has been pulled into NiFiCompletion StrategyfalseCompletion StrategytruefalsefalseMove Destination DirectoryThe directory to the move the original file to once it has been fetched from the file system. This property is ignored unless the Completion Strategy is set to "Move File". If the directory does not exist, it will be created.Move Destination DirectoryfalseMove Destination DirectoryfalsefalsetrueMove Conflict StrategyThe existing destination file should remain intact. The newly ingested file should be moved to the destination directory but be renamed to a random filenameRenameRenameThe newly ingested file should replace the existing file in the Destination DirectoryReplace FileReplace FileThe existing file should in the Destination Directory should stay intact and the newly ingested file should be deletedKeep ExistingKeep ExistingThe existing destination file should remain intact and the incoming FlowFile should be routed to failureFailFailRenameIf Completion Strategy is set to Move File and a file already exists in the destination directory with the same name, this property specifies how that naming conflict should be resolvedMove Conflict StrategyfalseMove Conflict Strategytruefalsefalsefalse30 secFile to Fetch/Your/Path/To/Salesforce_login.txtCompletion StrategyNoneMove Destination DirectoryMove Conflict StrategyRename00 secTIMER_DRIVEN1 secLoad Salesforce.com Login DatatrueAny FlowFile that could not be fetched from the file system for any reason other than insufficient permissions or the file not existing will be transferred to this Relationship.failuretrueAny FlowFile that could not be fetched from the file system because the file could not be found will be transferred to this Relationship.not.foundtrueAny FlowFile that could not be fetched from the file system due to the user running NiFi not having sufficient permissions will be transferred to this Relationship.permission.deniedfalseAny FlowFile that is successfully fetched from the file system will be transferred to this Relationship.successSTOPPEDfalsetrueorg.apache.nifi.processors.standard.FetchFile628138c7-31f1-4b60-892f-50ccc46744d9ab129a1d-2ba7-42ce-8757-cd47fe4e114b1012.1947620167502-10.89491056532296WARN1TIMER_DRIVEN1EVENT_DRIVEN0CRON_DRIVEN1TIMER_DRIVEN0 secCRON_DRIVEN* * * * * ?HTTP MethodGETHTTP request method (GET, POST, PUT, DELETE, HEAD, OPTIONS). Arbitrary methods are also supported. Methods other than POST and PUT will be sent without a message body.HTTP MethodfalseHTTP MethodtruefalsetrueRemote URLRemote URL which will be connected to, including scheme, host, port, path.Remote URLfalseRemote URLtruefalsetrueSSL Context ServiceThe SSL Context Service used to provide client certificate information for TLS/SSL (https) connections.SSL Context Servicefalseorg.apache.nifi.ssl.SSLContextServiceSSL Context ServicefalsefalsefalseConnection Timeout5 secsMax wait time for connection to remote service.Connection TimeoutfalseConnection TimeouttruefalsefalseRead Timeout15 secsMax wait time for response from remote service.Read TimeoutfalseRead TimeouttruefalsefalseInclude Date HeaderTrueTrueFalseFalseTrueInclude an RFC-2616 Date header in the request.Include Date HeaderfalseInclude Date HeadertruefalsefalseFollow RedirectsTrueTrueFalseFalseTrueFollow HTTP redirects issued by remote server.Follow RedirectsfalseFollow RedirectstruefalsefalseAttributes to SendRegular expression that defines which attributes to send as HTTP headers in the request. If not defined, no attributes are sent as headers. Also any dynamic properties set will be sent as headers. The dynamic property key will be the header key and the dynamic property value will be interpreted as expression language will be the header value.Attributes to SendfalseAttributes to SendfalsefalsefalseBasic Authentication UsernameThe username to be used by the client to authenticate against the Remote URL. Cannot include control characters (0-31), ':', or DEL (127).Basic Authentication UsernamefalseBasic Authentication UsernamefalsefalsefalseBasic Authentication PasswordThe password to be used by the client to authenticate against the Remote URL.Basic Authentication PasswordfalseBasic Authentication PasswordfalsetruefalseProxy HostThe fully qualified hostname or IP address of the proxy serverProxy HostfalseProxy HostfalsefalsefalseProxy PortThe port of the proxy serverProxy PortfalseProxy PortfalsefalsefalsePut Response Body In AttributeIf set, the response body received back will be put into an attribute of the original FlowFile instead of a separate FlowFile. The attribute key to put to is determined by evaluating value of this property. Put Response Body In AttributefalsePut Response Body In AttributefalsefalsetrueMax Length To Put In Attribute256If routing the response body to an attribute of the original (by setting the "Put response body in attribute" property or by receiving an error status code), the number of characters put to the attribute value will be at most this amount. This is important because attributes are held in memory and large attributes will quickly cause out of memory issues. If the output goes longer than this value, it will be truncated to fit. Consider making this smaller if able.Max Length To Put In AttributefalseMax Length To Put In AttributefalsefalsefalseDigest AuthenticationtruetruefalsefalsefalseWhether to communicate with the website using Digest Authentication. 'Basic Authentication Username' and 'Basic Authentication Password' are used for authentication.Use Digest AuthenticationfalseDigest AuthenticationfalsefalsefalseAlways Output ResponsetruetruefalsefalsefalseWill force a response FlowFile to be generated and routed to the 'Response' relationship regardless of what the server status code received is or if the processor is configured to put the server response body in the request attribute. In the later configuration a request FlowFile with the response body in the attribute and a typical response FlowFile will be emitted to their respective relationships.Always Output ResponsefalseAlways Output ResponsefalsefalsefalseTrusted HostnameBypass the normal truststore hostname verifier to allow the specified remote hostname as trusted. Enabling this property has MITM security implications, use wisely. Will still accept other connections based on the normal truststore hostname verifier. Only valid with SSL (HTTPS) connections.Trusted HostnamefalseTrusted HostnamefalsefalsefalseAdd Response Headers to RequesttruetruefalsefalsefalseEnabling this property saves all the response headers to the original request. This may be when the response headers are needed but a response is not generated due to the status code received.Add Response Headers to RequestfalseAdd Response Headers to RequestfalsefalsefalseContent-Type${mime.type}The Content-Type to specify for when content is being transmitted through a PUT or POST. In the case of an empty value after evaluating an expression language expression, Content-Type defaults to application/octet-streamContent-TypefalseContent-TypetruefalsetrueUse Chunked EncodingtruetruefalsefalsefalseWhen POST'ing or PUT'ing content set this property to true in order to not pass the 'Content-length' header and instead send 'Transfer-Encoding' with a value of 'chunked'. This will enable the data transfer mechanism which was introduced in HTTP 1.1 to pass data of unknown lengths in chunks.Use Chunked EncodingfalseUse Chunked EncodingtruefalsefalsePenalize on "No Retry"truetruefalsefalsefalseEnabling this property will penalize FlowFiles that are routed to the "No Retry" relationship.Penalize on "No Retry"falsePenalize on "No Retry"falsefalsefalsefalse30 secHTTP MethodPOSTRemote URLhttps://test.salesforce.com/services/oauth2/tokenSSL Context ServiceConnection Timeout5 secsRead Timeout15 secsInclude Date HeaderTrueFollow RedirectsTrueAttributes to SendBasic Authentication UsernameBasic Authentication PasswordProxy HostProxy PortPut Response Body In AttributeMax Length To Put In Attribute256Digest AuthenticationfalseAlways Output ResponsefalseTrusted HostnameAdd Response Headers to RequestfalseContent-Typeapplication/x-www-form-urlencodedUse Chunked EncodingfalsePenalize on "No Retry"false00 secTIMER_DRIVEN1 secSalesforce User/Pass OAuth2 LoginfalseThe original FlowFile will be routed on any type of connection failure, timeout or general exception. It will have new attributes detailing the request.FailurefalseThe original FlowFile will be routed on any status code that should NOT be retried (1xx, 3xx, 4xx status codes). It will have new attributes detailing the request.No RetrytrueThe original FlowFile will be routed upon success (2xx status codes). It will have new attributes detailing the success of the request.OriginalfalseA Response FlowFile will be routed upon success (2xx status codes). If the 'Output Response Regardless' property is true then the response will be sent to this relationship regardless of the status code received.ResponsefalseThe original FlowFile will be routed on any status code that can be retried (5xx status codes). It will have new attributes detailing the request.RetrySTOPPEDfalsetrueorg.apache.nifi.processors.standard.InvokeHTTP4eea2682-95d6-4dc2-9b43-0d58cc6114cdab129a1d-2ba7-42ce-8757-cd47fe4e114b1578.1929113378937-16.495102251998333DEBUG1TIMER_DRIVEN1EVENT_DRIVEN0CRON_DRIVEN1TIMER_DRIVEN0 secCRON_DRIVEN* * * * * ?Log LeveltracetracedebugdebuginfoinfowarnwarnerrorerrorinfoThe Log Level to use when logging the AttributesLog LevelfalseLog LeveltruefalsefalseLog PayloadtruetruefalsefalsefalseIf true, the FlowFile's payload will be logged, in addition to its attributes; otherwise, just the Attributes will be logged.Log PayloadfalseLog PayloadtruefalsefalseAttributes to LogA comma-separated list of Attributes to Log. If not specified, all attributes will be logged.Attributes to LogfalseAttributes to LogfalsefalsefalseAttributes to IgnoreA comma-separated list of Attributes to ignore. If not specified, no attributes will be ignored.Attributes to IgnorefalseAttributes to IgnorefalsefalsefalseLog prefixLog prefix appended to the log lines. It helps to distinguish the output of multiple LogAttribute processors.Log prefixfalseLog prefixfalsefalsetruefalse30 secLog LeveldebugLog PayloadtrueAttributes to LogAttributes to IgnoreLog prefix00 secTIMER_DRIVEN1 secFailure loggingtrueAll FlowFiles are routed to this relationshipsuccessSTOPPEDtruetrueorg.apache.nifi.processors.standard.LogAttribute0face432-ec9c-4a39-802c-90b628fc19bcab129a1d-2ba7-42ce-8757-cd47fe4e114b1013.7950139575373197.8627467178082WARN1TIMER_DRIVEN1EVENT_DRIVEN0CRON_DRIVEN1TIMER_DRIVEN0 secCRON_DRIVEN* * * * * ?Destinationflowfile-contentflowfile-contentflowfile-attributeflowfile-attributeflowfile-contentIndicates whether the results of the JsonPath evaluation are written to the FlowFile content or a FlowFile attribute; if using attribute, must specify the Attribute Name property. If set to flowfile-content, only one JsonPath may be specified, and the property name is ignored.DestinationfalseDestinationtruefalsefalseReturn Typeauto-detectauto-detectjsonjsonscalarscalarauto-detectIndicates the desired return type of the JSON Path expressions. Selecting 'auto-detect' will set the return type to 'json' for a Destination of 'flowfile-content', and 'scalar' for a Destination of 'flowfile-attribute'.Return TypefalseReturn TypetruefalsefalsePath Not Found BehaviorwarnwarnignoreignoreignoreIndicates how to handle missing JSON path expressions when destination is set to 'flowfile-attribute'. Selecting 'warn' will generate a warning when a JSON path expression is not found.Path Not Found BehaviorfalsePath Not Found BehaviortruefalsefalseNull Value Representationempty stringempty stringthe string 'null'the string 'null'empty stringIndicates the desired representation of JSON Path expressions resulting in a null value.Null Value RepresentationfalseNull Value Representationtruefalsefalseaccess_tokenaccess_tokentrueaccess_tokenfalsefalsefalsefalse30 secDestinationflowfile-attributeReturn Typeauto-detectPath Not Found BehaviorignoreNull Value Representationempty stringaccess_tokenaccess_token00 secTIMER_DRIVEN1 secGet Access TokentrueFlowFiles are routed to this relationship when the JsonPath cannot be evaluated against the content of the FlowFile; for instance, if the FlowFile is not valid JSONfailurefalseFlowFiles are routed to this relationship when the JsonPath is successfully evaluated and the FlowFile is modified as a resultmatchedtrueFlowFiles are routed to this relationship when the JsonPath does not match the content of the FlowFile and the Destination is set to flowfile-contentunmatchedSTOPPEDtruetrueorg.apache.nifi.processors.standard.EvaluateJsonPath0011Salesforce REST API Login1f990f6a5-841c-4d59-8a0e-08744febdc62Salesforce Integration806b9ea8-20f0-42f6-a65d-4ade3162b3b9LendingPointdc52d98f-8c02-4ff2-96b5-970116d2b3a3NiFi Flow0504/03/2016 05:28:13 EDT