Generate the application

The XML file which contains the Mobile Authenticator Studio customization data is located in \CustomizationTool\input\xml. For information about how to use the XML customization file, see Chapters Configure Mobile Authenticator Studio provisioning with standard activation to Configure miscellaneous functionalities.

The XML customization file(s) must be UTF-8 encoded.

In the course of the application generation process, the XML file is validated against DIGIPASS.xsd (located in the \CustomizationTool\core folder) and through functional checks. The XSD file defines the elements and attributes that can be defined in the XML customization file.

The XML file can be validated against the XSD file prior to customization by using an XML validation tool (e.g. the XML Tools plug-in of Notepad++).

Fill the XML customization file with Mobile Authenticator Studio customization data, and provide all necessary files in the appropriate folders. After this has been done, you can generate the customized Mobile Authenticator Studio binaries using the Customization Tool. This tool provides a graphical user interface (GUI) and a command line interface (CLI).

Since Mobile Authenticator Studio 4.7.3, the application name displayed to the user on the phone screen, is no longer an input of the Customization Tool. Presently, it is an attribute of the XML configuration file. It is defined by the applicationName attribute of the DIGIPASS element.

Since Mobile Authenticator Studio 4.12.0, the application supports ATS (App Transport Security) on iOS.

For Android applications:

When generating an application for Android with the Push Notification feature enabled, the Binary name property should be set to match package_name in the google-services.json file. The build will fail otherwise.

Android Asset Packaging Tools is untrusted on macOS, because it is not distributed via the AppStore. If you see a gatekeeper warning message, follow the instructions on the Apple support page from the provided URL.