Rebar iOS Data in Transit

Monkton, Inc. 2019

Part of Rebar's compliance with NIAP and other associated security profiles is adherence to the API Boundary for Data in Transit (DIT). DIT compliance for the app is achieved by extending Rebar's RebarWrapper class.

When implemented, RebarWrapper will encapsulate all the functionality necessary to make compliant HTTPS/TLS calls.

At this time, Rebar only implements HTTPS/TLS server calls. Other protocols will be implemented in the future.

Web Service Configuration

Rebar's RebarWrapper relies on interacting with the Rebar Middleware. The Rebar Middleware acts as a secure proxy to backend web services within your system, leveraging authentication mechanisms like JWT.

The middleware allows you to define web service connections to backend systems. Those hooks can be accessed within your app with the RebarWrapper class by simply calling the Web API methods.

Leveraging RebarWrapper

RebarWrapper encapsulates all the functionality necessary to make secure HTTPS calls over TLS using NIAP compliant algorithms. The implementation ensures that simple calls are necessary to invoke server API methods.

The RebarWrapper is intended to be used with the Rebar's API Endpoint for APIs.

With the API Endpoints, all that needs to be specified as the URL value is the Usable API Path from the Endpoint screen.

class RebarAppWrapper : RebarWrapper {
		Perform a server GET
	func myGet() {
		self.get("api/demoapp/my-get-method", contentType: RebarWrapper.JSON_CONTENT_TYPE, headers: nil);
		Perform a server PUT
	func myPut() {
		self.put("api/demoapp/my-put-method", contentType: RebarWrapper.JSON_CONTENT_TYPE, headers: nil, post: ["some-key":"some value"]);
		Perform a server POST
	func myCreate(email: String!, password: String!, fullName: String!) {
		let credentials: [String:AnyObject] = ["email":email, "password": password, "name": fullName];"api/demoapp/add-some-account", contentType: RebarWrapper.JSON_CONTENT_TYPE, headers: nil, post: credentials);

Invoking a Wrapper Class

Rebar's HTTPS wrapper is meant to be simple to develop against. We provide three closure/block handlers to handle different states of the request. Rebar expects most requests to be JSON data, thus the getJson methods for the RebarSecureResponse class.

  • successfulRequest provides the response data from the server if the request is successful.
  • failedRequest provides feedback to why the request failed. Rebar generally handles most of the error process and the willLogoff flag MUST be respected to go no further. The getApiError()?.show should be invoked with a UIViewController as a parameter.
  • cleanupRequest provides the means to cleanup the response after either a success or failure.

	var appWrapper: RebarAppWrapper? = nil;
	func callServer() {
		// Set our wrapper handler
		self.appWrapper = RebarAppWrapper();
		// Registration is complete now, cleanup
		self.appWrapper?.cleanupRequest = {
			self.appWrapper = nil;
		// What to do when there is a successful request
		self.appWrapper?.successfulRequest = {(response: RebarSecureResponse!) in
			// Grab the contents if applicable
			if let contents: [String:AnyObject] = response.getJson()!.dictionaryObject? {
				if let account = contents["account"] as! [String:AnyObject]! {
					// Do something here...
		// What to do when the request fails
		self.appWrapper?.failedRequest = {(response: RebarSecureResponse!, willLogoff: Bool) in
			guard !willLogoff else {
				// If we have logged off, do nothing and exit. Rebar
				// handles the rest
			// Show the error message now
		// Push keypair

Last Updated: February 04, 2019