NiFi Ingest 25.1
NiFi Ingest

# HandleAciRequest

Handles incoming ACI requests.

TIP: OpenText provides a template that includes all of the components necessary to handle ACI requests. For more information about how to handle actions in NiFi Ingest, see Handle Connector Actions.

## Properties

Name | Description
--- | ---
ACI context service | An AciContextServiceImpl Controller Service that stores information about actions that have been sent to NiFi Ingest.
IDOL License Service | To accept encrypted actions from components using an OEM license, set this property to an instance of IdolOEMLicenseServiceImpl.
Listening Port | The port to listen on for incoming ACI requests.
Hostname | The host name to bind to. If you do not set this property, the processor binds to all hosts.
SSL Context service | An IdolSSLConfigServiceImpl to configure SSL for incoming requests.
Authorized DN Pattern | A regular expression to apply against the Distinguished Name of each incoming connection. If the pattern does not match the DN, the connection is refused. After specifying an SSL Context Service, connections must be made over SSL but client authentication is not necessary unless you set this property as well. If you set this property, then users who want to make requests must supply a client certificate. The processor only accepts a request if the subject of the client certificate matches the specified regular expression. For example, you could set this property to: `CN=.*,OU=USERS,OU=NIFI` If you set this property to `.*`, any client certificate is accepted, provided it is signed by a trusted authority.
Max Request Header Size | The maximum size of an HTTP request header in bytes.
Multipart Parameters | A comma-separated list of regular expressions, to identify action parameters where you want to write the parameter value into the output FlowFile as multipart data, instead of to a FlowFile attribute.
Synchronous actions | A comma-separated list of regular expressions, used to identify synchronous action names.
Dynamic properties | Adding a dynamic property creates a new output relationship with the same name. The value of the dynamic property is a regular expression that matches action names. Actions that have a matching name are routed to the corresponding relationship. The actions `GetStatus` and `QueueInfo` are handled internally by this processor and cannot be overridden.

Copyright 2018-2024 Open Text
Version 25.1 | Last updated January 2025

Send documentation feedback

Close

Send documentation feedback

To send feedback using your default email client, open an email window.

Otherwise, send your feedback and the information below to MFI-swpdl.idoldocsfeedback@opentext.com.

We appreciate your feedback!

Product: Knowledge Discovery NiFi Ingest 25.1

Topic Title: HandleAciRequest