Classes

ACActiveSession describes a currently active Activeconnect session. Instances of this class are created in response to calls to ACMobileDevice.get_active_sessions. A session is considered active if the user has been authenticated and not logged out. ACActiveSession can be used to display and end a user’s sessions.

Represents the content of an authentication request Push Notification. Client applications should not create instances directly but rely on ACNotificationHandler to create a populate the instance. ACAuthenticationRequest is passed to ACAuthenticationViewController, which will decode the content, present appropriate UI to collect data and send results to server.

Class the represents a mobile device registered with Activeconnect. Instances of this class contain the information required to communicate with Activeconnect on behalf the of the device user. The client applicaton is responsible for storing the ACMobileDevice data for the user accounts registered with their app. ACMobileDevice data can be serialized as JSON and store/read from a secure location, for example the device key chain.

ACNotification handler parses the content of a push notification and extracts Activeconnect information. If the push notification is an Activeconnect authentication request the delegat’s presentAuthenticationUI is called with the decoded authentication request and the device that the request is for. The client should call the processNotification method when it receives a push notification. If processNotification indicates that the notification is an Activeconnect notification no further action is required. The client should carry out notification specific actions by implementing the ACNotificationHandlerDelegate protocol.

Represents the status of an Activeconnect session. When the status of a session changes, Activeconnect sends a Push Notification to the application. ACNotificationHandler creates an instance of this class and calls its delegate with the session status. The application can update its UI to notify the user that the status of the session has change.

The Management API provides utility methods for managing Activeconnect applications. The API is used for managing users.

View controller for the the acceptance part of the authentication process. The Activeconnect Framework includes a default UI for this authentication stage. ACAcceptanceViewControllers are created by ACAuthenticationViewController. A custom UI can be provided by creating a nib file containing an ACAcceptanceViewController and set the values of ACAuthenticationViewController.acceptanceBundleIdentifier and ACAuthenticationViewController.acceptanceNibName.

View controller that controls the authentication process. The Activeconnect framework provides a default UI for all stages of the. Applications can provide their own UI but must use this class to control the authentication process. Customization is achieved by providing Bundle and Nib informtion for each of the screens. The custom views must be instances or specializations of Activeconnect view controller classes

Class used to display a ‘busy’ screen, which is displayed when the application is performing a lengthy task. Client applications can use this class to create a custom busy UI. Create a new view controller in Interface Builder, then set the Custom Class property to ACBusyViewController in the Identity Inspoector. The bundle identifier and nib containing the view can then be used with ACAuthenticationViewController.authenticatingBundleIdentifier and ACAuthenticationViewController.authenticatingNibName to display the view.

A view controller that collects images of the user’s face.

View controller for performing OS authentication. ACOSViewControllers are created by ACAuthenticationViewController. A custom UI can be provided by creating a nib file containing an ACOSViewController and set the values of ACAuthenticationViewController.osBundleIdentifier and ACAuthenticationViewController.osNibName.

View controller used to detect proximity when it is required by an Authentication Request. A custom UI can be provided by creating a nib file containing an ACProximityViewController and set the values of ACAuthenticationViewController.proximityBundleIdentifier and ACAuthenticationViewController.proximityNibName.

View controller that informs the user that training is required. Activeconnect includes a default UI for this view controller. A custom UI can be provided by creating a nib file containing an ACTrainingRequiredViewController and set the values of ACTrainingViewController.instructionsBundleIdentifier and ACTrainingViewController.instructionsNibName.

View controller used for the training process. The view controller has several views which are displayed depending upon the training that needs to be performed. In addition the following views are controller:

• Instructions view is displayed prior to training and a status view which displays the result
• Busy view is displayed while training data is being processed.
• Status view is displayed to report the result of the training process.