App Permissions
The Fabasoft App requires certain app permissions for particular actions. When the app tries to execute such functions, a dialog is displayed by the operating system to provide access.
The Fabasoft App must be secured with an app passcode. The additional app passcode is an extra layer of security in order to protect the data stored on your device. If you switch the app to background for more than 15 seconds, or keep it open for more than 5 minutes without interaction, the app will be automatically locked. In order to unlock the app, you must identify yourself via the app passcode or biometric identification. The app code must consist of at least six digits.
If the passcode is entered incorrectly 5 times, all data in the app will be erased.
In case the dialog for biometric identification is accidentally closed, you can reopen it via the biometric ID button at the bottom left.
The following login methods are supported by the Fabasoft App (dependent upon the respective Fabasoft Folio or Fabasoft eGov-Suite installation).
To log into the Fabasoft App, proceed as follows:
Note: The backend URL and the available login methods are definable via Mobile Device Management.
For further information please visit:
https://help.folio.fabasoft.com/index.php?topic=doc/Mobile-Device-Management/index.htm: new window
Authentication with Client Certificates
The Fabasoft App supports authentication with client certificates. On Android devices, the client certificates stored on the device in the systems key store can be used.
On iOS, apps are not allowed to access the system key chain to get access to globally deployed certificates. However, if required, it is possible to import a client certificate into the app. This can be done either by importing a PKCS#12 file into the Fabasoft App using Finder (macOS only), or by opening a file with the extension pfx.fabasoft in the Fabasoft App using the “Open in” feature of another app. The certificate file must include the private key so that it can be used for authentication. The certificate is securely stored in the key chain of the device.
However, when you use the permanent login feature (activate “Stay logged in” on the login page) with the “Single Sign-On” login method (using a SAML identity provider; requires Fabasoft Folio 2020 Update Rollup 2 or later as backend system), the authentication is delegated to a Safari web view which has access to the system key chain as well. In general, mobile device management software allows to distribute client certificates that can be used in Safari. In this case, the client certificate does not need be stored in the context of the Fabasoft App.
Note: The worklist on the Apple Watch does not support authentication with client certificates.
Additional Services
If you want to add an additional Fabasoft service, proceed as follows:
Note: Only services with secure connections (HTTPS) are allowed.
For more information, see chapter ”Cloud Services”
When performing a long tap on the app icon on the home screen of your device, you can directly navigate to “Worklist”, “Favorites”, or “Search” or you can enter the “Offline Mode”.