User manual

PaperCut - Sharp OSA Manual 2014-12-24

2.5.7 Additional Network Security (optional)

The MFP communicates with the PaperCut server over the network (e.g. to

authenticate users or release print jobs). To provide an additional level of security,

PaperCut may be configured to only allow device connections from a restricted range

of network addresses. This ensures that only approved devices are connected to the

PaperCut server.

By default PaperCut will allow device connections from any network address. To

restrict this to a subset of IP addresses or subnets:

1. Logon to the PaperCut administration web interface at http://<papercut-

server>:9191/admin

2. Go to the OptionsAdvanced tab and find the “Security” section.

3. In the “Allowed device IP addresses” field enter a comma-separated list of

device IP addresses or subnets (in the format <ip-address>/<subnet-mask>).

4. Press the “Apply” button.

5. Test the devices to ensure they can continue to contact the PaperCut server.

2.6 Using Swipe Card Readers

Sharp devices support the following keyboard emulating USB card readers:

 Elatec TWN3 prox card readers

 MAGTEK Swipe Reader Model # 21040110

 RF IDEAS AIR ID Enroll Proximity Reader Model # RDR-7081AKU

Other keyboard emulating card readers may work, but should be tested prior to

deployment.

To use a swipe card reader for authentication:

1. Connect the reader to a USB port of the device.

2. In the PaperCut administration interface, click the device entry on the

‘Devices’ tab and check the ‘Swipe Card Reader’ option in ‘External

Device Settings -> Authentication methods’.

Some card readers might need additional configuration, please see the Advanced

Configuration section for details.

2.7 Upgrading to a newer version

The embedded application will be up to date when you upgrade your PaperCut

installation, no further action is necessary.

3 Post-install testing

After completing installation and basic configuration it is recommended to perform

some testing of the common usage scenarios. This important for two reasons:

1. To ensure that the embedded application is working as expected.