[MINIFI-238] MiNiFi Initial Command and Control Server Implementation

• Type: New Feature
• Status: Resolved
• Priority: Major
• Resolution: Done
• Fix Version/s: 0.2.0
• Component/s: Command and Control
• Assignee: Bryan Rosander
• Reporter: Bryan Rosander
• Created: 15/Mar/17 16:20
• Updated: 20/Apr/17 20:21
• Resolved: 31/Mar/17 16:27

Description

A lot of work (MINIFI-2, MINIFI-4, MINIFI-12, MINIFI-14, MINIFI-17, MINIFI-36) has gone into creating a configurable way for MiNiFi to get new configuration from a defined source.

This is one aspect of the overal the command and control feature proposoal. The other aspect is an endpoint that ties into the NiFi ideas of flow versioning and probably the variable registry.

While the flow registry is not available for consumption yet, we can still start proving out things from the MiNiFi end forward. We can start by implementing a server MiNiFi can get configuration from that is done in a pluggable way such that it can be integrated with the NiFi registries mentioned above when they are ready for consumption.

This server should:
1. Utilize same/similar paradigms of the NiFi webserver to facilitate reuse and possible future embedding.
2. Support pluggability for its main functions including security and logic for retrieving the MiNiFi configuration.
3. Support both authentication of users and authorization for a given flow.
4. Integrate easily with the existing PullHttpChangeIngestor in MiNiFi.

Issue Links

• relates to: MINIFI-272 Hierarchical C2 support
• links to: GitHub Pull Request #75