Aurena Native Apps
IFS Aurena Native Apps are the actual Aurena Native applications which need to be installed on a device. IFS Aurena Native Apps are distributed through the standard channels for the main different platforms in use.
More information on IFS Aurena Native Apps can be found here.
In order to install an IFS Aurena Native App you need to fetch the app through the standard channels for the different platforms:
- Google Play (Android devices)
- Apple App Store (iOS devices)
- Windows Store (Windows devices)
When the IFS Aurena Native Apps is available via a store you search for the IFS Aurena Native App and download it to your own device.
Further reading about the installation of a specific IFS Aurena Native App is explained in Aurena Native Business Apps and the applicable release notes for that IFS Aurena Native App.
Several of IFS Aurena Native Apps can be configured in order to show which fields should be displayed, in which state to fetch notifications, time range format etc.
How and what configuration that exists for a certain app is explained in Aurena Native Business Apps.
In order to log in to an IFS App on a device, you need to specify
- the Server-URL relevant for the IFS Cloud installation
- user name and password
To acquire the Server-URL, please contact your organization’s IFS administrator.
In some situations IFS Cloud server and/or the Open ID authentication provider will be deployed using a SSL certificate that is not issued by a well known certificate authority (e.g.: self signed SSL certificates). In such a situation it may become necessary to install such certificates used by the Identity Provider Server on to the device where Aurena Native application will be used from. In some situations it may be necessary to install the complete certificate chain. Certificate trust varies on different mobile OS versions and also depends on the level of security enforced by each mobile platform.
Please note that for Touch Apps and Aurena Native apps to work properly, the Middleware server needs to have the fully qualified certificate chain. The root certificate and the intermediate certificate need to be linked. If there are any servers in between (proxy server, load balancer, etc), this server is also expected to have the fully qualified certificate chain.
OpenID Connect Provider Configuration
This part describes the configuration that must be done on the Identity Provider which is configured in the system in order to enable users to authenticate to the different Touch Apps.
Please refer to Authentication configurations for the steps that must be followed to allow external access to the Authentication Provider end point of the IFS Middleware Server if using DB Authentication.
Touch Apps that support OpenID Connect authentication also have their own Redirect URIs. This will typically be of the format * ifs-app.com.ifsworld.#uniqueAppName#://app.* These redirect URIs must be configured in the Identity Provider used in the system. Consult the documentation for the specific apps for the exact redirect URI that must be registered for each Touch App.
Please refer to Authentication configurations for the exact steps that must be followed to setup these redirect URIs on the identity provider that is being used in your system.
Push Notification Hubs
Each app requires its own Notification Hub if it supports push. Customers can share a Notification Hub with other customers or create their own. If they create their own they will need to know the registration details for the app on all device platforms that they wish to use. Some of this registration information is sensitive information (passwords, secret keys).
The Notification Hub connection details need to be setup in the IFS Cloud database. The connection string is sensitive information.
You need to contact IFS in order to get the Push Notification Hub to be set up.
How to use an app is described in the same section as the configuration for a certain app: Aurena Native Business Apps.