Name: nifi-ios-s2s
Owner: Hortonworks Inc
Description: Repository for an iOS client library for Apache NiFi
Created: 2017-05-31 18:50:44.0
Updated: 2017-09-05 13:28:46.0
Pushed: 2017-10-04 20:38:46.0
Homepage: null
Size: 195
Language: Objective-C
GitHub Committers
| User | Most Recent Commit | # Commits |
|---|
Other Committers
| User | Most Recent Commit | # Commits |
|---|
A lightweight, easy-to-use, Cocoa Framework for sending data to NiFi via the Site-to-Site protocol implemented in Objective-C with primarily Apple-provided Objective-C/C library dependencies. Synchronous and asynchronous interface methods are provided via a low-level site-to-site client and a higher-level site-to-site service that wraps the client. This Cocoa framework will run on iOS devices and simulators.
For the most part, this implementation uses dependencies provided by the Apple platform. The one exception to this is the third-party FMDB, a lightweight SQLite interface, which is used internally by s2s as a mechanism for persistent queuing of flow file data packets when the asynchronous interface is invoked.
The included XCode Project (nifisitetosite.xcodeproj) can be used for building using the XCode IDE or XCode command-line tools.
Here are the commands for building and running the test suite from the command line:
hage bootstrap
ebuild test -scheme s2sTests -destination 'platform=iOS Simulator,name=iPhone 7'
The first command will run Carthage in the project directory. It uses the top-level Cartfile as its input and will download and build FMDB. The second command builds s2s and s2sTests, which are run in the specified destination, in this case an iPhone 7 iOS Simulator device.
The included XCode project case also be opened in the XCode IDE, as its own standalone project or added to a workspace containing another project (e.g., the app for which you want to use the s2s framework).
Here is a basic usage example of the s2s Cocoa Framework from Objective-C.
SiteToSiteRemoteClusterConfig *remoteNiFiInstance =
[NiFiSiteToSiteRemoteClusterConfig configWithUrl:[NSURL URLWithString:@"http://localhost:8080"]];
SiteToSiteClientConfig *s2sConfig = [NiFiSiteToSiteClientConfig configWithRemoteCluster: remoteNiFiInstance];
onfig.portName = @"From iOS";
2sClient = [NiFiSiteToSiteClient clientWithConfig:s2sConfig];
ransaction = [s2sClient createTransaction];
ctionary * attributes1 = @{@"packetNumber": @"1"};
ta * data1 = [@"Data Packet 1" dataUsingEncoding:NSUTF8StringEncoding];
ataPacket1 = [NiFiDataPacket dataPacketWithAttributes:attributes1 data:data1];
nsaction sendData:dataPacket1];
ctionary * attributes2 = @{@"packetNumber": @"2"};
ta * data2 = [@"Data Packet 2" dataUsingEncoding:NSUTF8StringEncoding];
ataPacket2 = [NiFiDataPacket dataPacketWithAttributes:attributes2 data:data2];
nsaction sendData:dataPacket2];
TransactionResult *transactionResult = [transaction confirmAndCompleteOrError:nil];
Note: For Objective-C apps, note that s2s assumes Automatic Reference Counting (ARC) and is not recomended for use in applications compiled in Manual Memory Management mode.
As an Objective-C Cocoa Framework, s2s also defines a Swift module and can be imported as such into a Swift or mixed-language project. The s2s API is nullability-hinted to assist Swift developers.
To use the s2s module in your Swift code, add the s2s.framework to your target's Linked Frameworks and Libraries, and then add this module import to the top of your .swift source code file:
rt s2s
For more background information on mixing Swift and Objective-C, see Apple's Developer Guide for mixing Objective-C and Swift. In this case, we are following the steps for Importing External Frameworks.
Below are basic usage examples of the s2s Cocoa Framework as a module in Swift.
s2sClientConfig = NiFiSiteToSiteClientConfig()
lientConfig.addRemoteCluster(NiFiSiteToSiteRemoteClusterConfig(url: URL(string: "http://localhost:8080")))
onfig.portName = "From iOS";
s2sClient = NiFiSiteToSiteClient(config: s2sClientConfig)
transaction = s2sClient.createTransaction()
data1 = NiFiDataPacket(attributes: ["packetNumber": "1"],
data: "Data Packet 1".data(using: String.Encoding.utf8))
saction?.sendData(data1)
data2 = NiFiDataPacket(attributes: ["packetNumber": "2"],
data: "Data Packet 2".data(using: String.Encoding.utf8))
saction?.sendData(data2)
let transactionResult = try transaction?.confirmAndCompleteOrError()
print("Sent", transactionResult!.dataPacketsTransferred, "packets!")
tch {
print(error.localizedDescription)
s2sClientConfig = NiFiSiteToSiteClientConfig()
lientConfig.addRemoteCluster(NiFiSiteToSiteRemoteClusterConfig(url: URL(string: "http://localhost:8080")))
onfig.portName = "From iOS";
data1 = NiFiDataPacket(attributes: ["packetNumber": "1"],
data: "Data Packet 1".data(using: String.Encoding.utf8))
data2 = NiFiDataPacket(attributes: ["packetNumber": "2"],
data: "Data Packet 2".data(using: String.Encoding.utf8))
packetsToSend = [data1, data2];
SiteToSiteService.sendDataPackets(packetsToSend, config: s2sClientConfig) { (transactionResult, error) in
print("Sent", transactionResult!.dataPacketsTransferred, "packets!")
rt s2s
..
arly in the app set your s2s client configuration
s2sClientConfig = NiFiQueuedSiteToSiteClientConfig()
lientConfig.addRemoteCluster(NiFiSiteToSiteRemoteClusterConfig(url: URL(string: "http://localhost:8080")))
onfig.portName = "From iOS";
lientConfig.dataPacketPrioritizer = NiFiNoOpDataPacketPrioritizer(fixedTTL: 60.0)
..
est Practice: Setup some form of periodic queue processing and cleaning events
queuedOperationCompleted(status: NiFiSiteToSiteQueueStatus?, error: Error?) {
// Process completion event
// The status parameter holds queue count, size, and an "isFull" flag.
cleanAndProcessQueue() {
NSLog("Cleaning and processing NiFi SiteToSite queue")
// Cleanup deletes queued packets based on maxQueueCount or maxQueueSize or if packets are older than their TTL
NiFiSiteToSiteService.cleanupQueuedPackets(with: self.s2sClientConfig,
completionHandler: self.queuedOperationCompleted)
// Process sends the next batch (based on configured batchCount or batchSize) to the remote NiFi
NiFiSiteToSiteService.processQueuedPackets(with: self.s2sClientConfig,
completionHandler: self.queuedOperationCompleted)
}
eProcessingTimer = Timer.scheduledTimer(timeInterval: queueProcessingInterval,
target: self,
selector: #selector(cleanAndProcessQueue),
userInfo: nil,
repeats: true)
..
t any point in the app, when we have data to send.
dataPacket = NiFiDataPacket(attributes: ["key1": "value1"],
data: "This is the content of the data packet".data(using: String.Encoding.utf8))
SiteToSiteService.enqueueDataPacket(dataPacket,
config: s2sClientConfig,
completionHandler: queuedOperationCompleted)
For a more complete example, see the included DemoSwift application.
The functionality of this framework is verified by two methods:
In addition to verifying functionality, these serve as good examples of how to use the framework API.
To run the tests, select 's2sTests' as the active scheme in XCode, switch to the Test Navigator in the left panel, and click the play icon next to a test or test suite to run the tests.
To run one of the demo apps, select 'DemoSwift' or 'Demo' as the active scheme in XCode and click the Build and Play scheme button.
The s2s framework uses Apple's NSURL family of APIs internally,
i.e. NSURLSession. You can customize this in NiFiSiteToSiteRemoteClusterConfig by specifying a custom
NSURLSessionConfiguration and/or
NSURLSessionDelegate.
This gives you a lot of flexibility and control regarding how connections are established to each remote NiFi cluster. Two specific types of connection configuration, secure connections and proxy settings, are covered in this document.
The S2S Framework can use TLS when communicating to a NiFI server, provided the NiFi server is configured for secure communication.
If a NiFi server is using a certificate signed by a trusted root Certificate Authority,
all that is required is to configure the site-to-site client with a https:// URL for the remote NiFi cluster. HTTPS will be used as the transport protocol.
If the NiFi server is using a self-signed certificate (e.g., a test environment), or your app needs to perform nonstandard TLS chain validation for some other reason, there is more you must do to make the system trust the CA. It is recommended you add that authority's trust anchor as described at the bottom of the Apple Secure Networking Guide. Alternatively, although not a recommended practice, you can override TLS chain validation with custom logic. The s2s framework uses Apple's NSURL family of APIs internally, i.e. NSURLSession. Therefore, in order to provide custom TLS chain validation your app must implement a URLSessionDelegate that overrides the function URLSession:didReceiveChallenge:completionHandler:. Within your authentication handler delegate method, you should check to see if the challenge protection space has an authentication type of NSURLAuthenticationMethodServerTrust, and if so, obtain the serverTrust information from that protection space.
An example of this is provided in DemoSwift's AppNetworking.swift file.
For more information, see “Performing Custom TLS Chain Validation” in Apple's URL Session Programming Guide for more information. You might also find these resources informative:
Client authentication to the NiFi server is supported in two ways:
For client certificate authentication, you must provide a client certificate and implement a URLSessionDelegate that responds to the server's TLS handshake challenge by providing a client certification as described in Apple's URL Session Programming Guide.
Note that due to a limitation of Apple's iOS platform, client certificate authentication is not compatible with background network tasks, as they are performed by a system process, and Apple's platform currently does not allow passing client credentials between processes. Therefore, if your app requires to make use of the s2s module in the background, it is recommended you use username/password client credentials, which are utilized in the library to communicate with the server to create an authentication token for site-to-site communication. For more information on this limitation of Apple's iOS platform, see: https://forums.developer.apple.com/thread/28713
When using the TCP_SOCKET transport protocol for SiteToSite (instead of the default HTTP), there is an additional step for securing the transport layer with an SSL Context.
Internally, this transport protocol is built using the CFStream API. You can pass through the TLS/SSL settings to use for the connection in the NiFiSiteToSiteRemoteClusterConfig.socketTLSSettings field. The settings are a NSDictionary, with key/values well documented in Apple's developer documentation for CFStreams:
If you do not set a value for the socketTLSSettings config field, the connection will be unsecure. If you want a secure connection using the iOS platform's default SSL settings (reasonable in most cases, assuming you are using a server certificate signed by a root, third-party CA) then pass an empty dictionary.
NiFi clusters cans be configured to be accessed via an HTTP/S proxy for the SiteToSite protocol. If this is how the remote NiFi cluster is configured, and you wish to
connect via a proxy, this is possible via the SiteToSiteConfig.urlSessionConfiguration field.
For information on how to do this, see the following resources:
Here is an Objective-C example:
tableDictionary *proxyConfigDictionary = [NSMutableDictionary dictionary];
yConfigDictionary[(NSString *)kCFProxyTypeHTTPS] = @(1);
yConfigDictionary[(NSString *)kCFProxyHostNameKey] = @"myproxy.example.com";
yConfigDictionary[(NSString *)kCFProxyPortNumberKey] = @(8080);
yConfigDictionary[(NSString *)kCFProxyUsernameKey] = @"proxyUsername";
yConfigDictionary[(NSString *)kCFProxyPasswordKey] = @"proxyPassword";
SiteToSiteRemoteClusterConfig *remoteClusterConfig = ...
teClusterConfig.urlSessionConfiguration = [NSURLSessionConfiguration defaultSessionConfiguration];
et other URL Session Configuration options as desired ...
teClusterConfig.urlSessionConfiguration.connectionProxyDictionary = proxyConfigDictionary;
Q: In my application logs I see, “Unable to discover port id for site-to-site input port with name '…'. Server returned status code '403'.“
A: This is a permissions issue with the user you are using to connect to the NiFi API. Check the Policies menu in the NiFI UI and make sure the user has an access policy for 'retrieve site-to-site details'.
Q: I cannot successfully send data over a secure connection. In my application logs I see, “ERROR An SSL error has occurred and a secure connection to the server cannot be made.“
A: TLS validation is failing, e.g., it could be that TLS chain validation of the server's certificate is failing. See the Security section above for how to configure your app to communicate over TLS.
Q: I cannot successfully send data over a secure connection. In my application logs I see, “kCFStreamErrorDomainSSL”
A: You are implementing custom TLS chain validation, but have not configured your app to allow that. You must add “Allow Arbitrary Loads”:YES to “App Transport Security Settings” dict in Info.plist. See Demo or DemoSwift's Info.plist file for an example.