MAF includes a configurable, multipurpose onboarding component. The Logon Core is separate from the Logon UI, to support the creation of custom Logon UIs. This layer contains code to execute logon operations. The component builds on SAP Mobile Platform libraries, such as OData Connectivity, Afaria client libraries, and Client Hub libraries.
Based on user input, the Logon Core determines which type of registration to execute.
After registration, the Logon Core:
- Checks if any scenario is configured to be forced.
- Triggers a test HTTP(S) request to the host, and the port specified by the user.
- Analyzes the response to this request based on:
- HTTP response code
- Cookies
- Response headers
The Logon Core then determines which communicator to use. If it cannot be determined, the logon falls back to HTTP Rest. If the decision flow can find a suitable communication setup, it report a success, otherwise the logon process stops with a failure message.
The default Logon UI supports customization of headers and footers and includes a fully
skinnable UI. This component builds on the MAF Logon Core, and provides a higher-level
integration API. These logon operations are supported by the integration API:
- Logon – register or unlock the secure store so that the app has access to server information and credentials to initiate requests.
- Change back-end password – update the backend password stored in the secure store of the client.
- Change secure store password (App Passcode) – change the password of the secure store.
- Lock secure store – force the secure store to lock itself while the application is still in the foreground.
- Delete user – unregister and delete all locally stored content from the secure store.
- Registration information – present information provided by the user during logon.
- Update application settings – get server settings from SAP Mobile Platform.
- Registration data – used by the application to get all registration data from MAF logon.