Developing with MAF Logon

MAF logon components consist of MAF Logon UI and MAF Logon Manager and support user onboarding.

MAF Logon UI presents logon screens on the device, providing easy integration for applications that use default logon UI behavior. While MAF Logon UI constructs a dynamic UI from context elements, MAF Logon Manager executes operations and constructs UI contexts to be presented by MAF Logon UI. Thus, MAF Logon Manager handles all UI-related configurations.

• Architectural Overview
  MAFLogonUING provides an out-of-the-box logon user interface that uses the default implementation of MAFLogonUIViewManager. This class handles navigation between various logon screens using the MAFLogonUIContextViewManager, which builds dynamic screen content from MAFLogonUIContext objects.
• MAF Logon Example
  Create a new xcode project. If you already have an existing project, check if it is configured correctly.
• Executing Logon Operations
  After you initialize MAFLogonUIViewManager, present the MAF logon UI screens. The View Manager maintains a reference to the LogonMediator (which, in the code examples, may also be called the logonManager). To present a particular screen, call the corresponding operation on the LogonMediator, which notifies the View Manager of MAFLogonUING that the action requires input. The View Manager generates and presents the input screen. The View Manager then calls back the LogonMediator in MAFLogonManagerNG and executes the next step of the requested operation.
• Data Requests
  After you complete the registration and initialize the secure store, you can request data from the back end.
• Mutual Certificate Handling
  MAF supports mutual certificate based data requests.
• Handling Delegate Calls
  The MAFLogonUING notifies applications about the result of each MAFLogonManagerNG operation it executes. The MAFLogonNGDelegate protocol must be implemented by your application’s View Controller.
• Error Handling
  MAFLogonManagerNG communicates errors using iOS-standard NSError objects. If the passed NSError object is not nil, an error is generated. MAF provides an error-handling method for these; the NSError instance contains the localized error description, the error domain, and the error code.
• Customizing the Logon UI
  To be able to use the customization options MAF Logon UI provides, implement MAFLogonUICustomizationDelegate in one of your classes.
• Logon Screen Configuration Options
  To change the behavior of MAFLogonManagerNG, adjust the feature and default values configuration files at build time. The plist format configuration files are located in the MAFLogonManagerNG.bundle folder. plist is an XML format that can be adjusted in Xcode or in any text editor.
• Afaria Support
  MAFLogonManagerNG fully supports Afaria-based configuration management, which is built into the library.
• MAF Onboarding Scenarios
  The MAF logon manager supports multiple onboarding scenarios, based on the most common infrastructure setups supported by enterprise mobile applications.
• MAF Configuration Provisioning
  SAP mobile applications are delivered with a default skin. You can change skinning parameters at runtime without recompiling the mobile application from the source. The skinning is based on metadata in an XML file. You must upload the styling content to the SAP Mobile Platform server that manages the application. Mobile applications also ship with a default structural configuration. As well as skinning, you can also structurally extend applications based on a metadata description.