Password protecting or encrypting files

Hosted Content

Since your web server is what controls who has access to your files, Kiosk Pro isn't able to password protect files on a remote server.  The app does support the following types of server-side authentication methods: 

• Default
• HTTP Basic
• HTTP Digest

If you are using an Apache web server, it is possible to password protect your files using .htaccess and .htpasswd files - more on how to set this up here and here.  

Local Content

There is currently no way of encrypting or hiding local files in Kiosk Pro. With that said, it's not possible for remote web pages to access files stored locally on the iPad so the only ways that local data might be copied would be:

• If you had a local page that deliberately sent the data to a remote server. As you are in control of the content you place on the iPad, this is under your control.
• If someone physically connected the iPad to a computer and downloaded the files. It is possible to prevent this by supervising the device, which allows you to set a number of restrictions on how the device can be used including the ability to sync with computers.

XML File for Remote Settings Control

There currently is no way of encrypting or password protecting the XML file used for Remote Settings Control. We recommend only including information that isn't considered sensitive in the file.

For example, if setting up a kiosk for email notifications, we'd recommend using an email address set up specifically for this purpose and not used for anything else as the sending email (as that is the email requiring a password). You can also set up the SMTP settings either directly on the iPads through the settings menu or you can add them in the initial .xml update and then remove them from future production versions of the .xml file.

By removing the entire Email Notifications section of the file once these settings have been placed, Kiosk Pro will just keep these settings as they are currently set (until you change them manually or add them back to the .xml file).

For example, to stop updating just the 'Password' field, you would remove or comment out the following from the .xml file (including the opening <dict> and closing </dict> tags:

<!--Password-->
	<dict>
		<key>Key</key><string>smtpPassword</string>
		<key>Value</key><string></string>
	</dict>

When using an .xml file automatically generated by the app using the Export Current Settings feature, the SMTP password is omitted by default.