Common Questions about Card Readers

KB Home   |   Common Questions about Card Readers

Main.CommonQuestionsAboutCardReaders History

Hide minor edits - Show changes to output

July 12, 2018, at 12:01 AM by Aaron Pouliot - Added category identification
Changed line 226 from:
''Categories:'' [[Category.PaperCutMF|+]]
to:
''Categories:'' [[Category.PaperCutMF|+]], [[Category.Identification|+]]
December 14, 2017, at 07:41 AM by Mel Zouzoulas - Removed sentence about providing Elatec files because the one have=out of date. Reseller or ASC
Changed lines 58-60 from:
You'll find more information about this in the FAQ question about changing card number formats below, and also in the manuals for the PaperCut embedded solutions.

''Note about Elatec readers:'' To change the output for Elatec readers you will need a configuration executable and some scripts. Support has four pre-built scripts to change the output between hex and decimal as well as reversing the output for each format. Contact support@papercut.com and ask for the TWN guide (PDF format) and the TWN resources zip file
.
to:
You'll find more information about this in the FAQ question about changing card number formats below, and also in the manuals for the PaperCut embedded solutions. Reach out to your reseller or PaperCut Authorized Solution Center (ASC).
September 12, 2017, at 01:22 AM by peterf - Added sections for two new features in 17.3
Added lines 199-225:
Q: My users employ their PIN instead of their network passwords to authenticate. Are they able to perform card self-association using their PIN?

A: We've spoken with a number of sites wherein users aren't privy to the passwords for their network accounts, and instead use a PIN exclusively. In the past, card self-association would require a user to authenticate with their formal network credentials, rendering it an unviable feature for those sites. As of PaperCut MF 17.3, it is now possible to authenticate during card self-association using a PIN instead of a password.

To enable PIN authentication for card self-association, you'll need to modify an advanced configuration key via the [[https://www.papercut.com/products/ng/manual/common/topics/sys-config-editor.html|Config Editor]]. The key in question:

[@ext-device.card-self-association.auth.allow-password-or-pin@]

By default, attempting to authenticate with a username and PIN when self-associating will fail. When the above configuration key is changed from @@N@@ to @@Y@@, self-association with either a username and PIN or a username and password will be possible.

Q: I maintain the PINs for my users within my domain user listing. Can I synchronize these with PaperCut MF in the same way that I synchronize card/ID numbers?

A: PIN synchronization with common directory services is achievable as of PaperCut MF 17.3. To get this working, you'll need to tell PaperCut MF what field to retrieve these PINs from in your directory listing; this is done using an advanced configuration key, modifiable via the [[https://www.papercut.com/products/ng/manual/common/topics/sys-config-editor.html|Config Editor]].

If your '''Primary sync source''' is configured to be '''Windows Active Directory''', the configuration key to populate with the name of your PIN field is as follows:

[@user-source.ad.user-pin-field@]

If your '''Primary sync source''' is set to '''LDAP''', you'll instead want to use this key:

[@ldap.schema.user-pin-field@]

Alternately, if you wish to retrieve PINs from an LDAP synchronization source which is configured as your '''Secondary sync source''', you'll need this key:

[@ldap.2.schema.user-pin-field@]

You can find more information about how to customize your synchronized LDAP fields in the following section of our online [[https://www.papercut.com/products/ng/manual/common/topics/ldap.html|User Manual]].
Changed line 189 from:
An alternate and popular option is "duel frequency" the cards using RFID data dots (RFID ID stickers).  Rather than using a multi-reader a single reader type is selected and cards not compatible with this reader have a data-dot sticker applied.  Care needs to be taken to ensure the data dotes selected don't clash with the physical cards.  We recommend careful testing to validate your selection prior to production deployment.
to:
An alternate and popular option is "dual frequency" the cards using RFID data dots (RFID ID stickers).  Rather than using a multi-reader a single reader type is selected and cards not compatible with this reader have a data-dot sticker applied.  Care needs to be taken to ensure the data dotes selected don't clash with the physical cards.  We recommend careful testing to validate your selection prior to production deployment.
July 18, 2014, at 04:47 PM by Don Jacobson - corrected spellling of "field"
Changed lines 94-95 from:
The common methods are 1 and 2 as these are simplest to implemented and most automated.  If you're using Microsoft Active Directory, a common selection is to re-use the ''pager number'' filed (not many people have pages these days so it's a good choice for a card number store!).
to:
The common methods are 1 and 2 as these are simplest to implemented and most automated.  If you're using Microsoft Active Directory, a common selection is to re-use the ''pager number'' field (not many people have pages these days so it's a good choice for a card number store!).
Changed lines 3-4 from:
''Note: This KB article is a work in progress. Please excuse any typo's''
to:
Changed lines 198-200 from:
A: Yes, you can enforce a minimum length by changing the value of the config key @@user.card-id-min-length@@. The default value is 1. You can set it to a value of your choice. You can change the value of a config key via @@Options -> Config Editor@@. Information on how to use a config editor is given [[https://www.papercut.com/products/ng/manual/sys-mgmt-config-editor.html| here]].

to:
A: Yes, you can enforce a minimum length by changing the value of the config key @@user.card-id-min-length@@. The default value is 1. You can set it to a value of your choice. Change the value of a config key via @@Options -> Config Editor@@. Information on how to use the config editor is given [[https://www.papercut.com/products/ng/manual/sys-mgmt-config-editor.html| here]].

Changed lines 198-200 from:
A: Yes, you can enforce a minimum length by changing the value of the config key @@user.card-id-min-length@@. The default value is 1. You can set it to a value of your choice. ou can change the value of a config key via @@Options -> Config Editor@@. Information on how to use a config editor is given [[https://www.papercut.com/products/ng/manual/sys-mgmt-config-editor.html| here]].

to:
A: Yes, you can enforce a minimum length by changing the value of the config key @@user.card-id-min-length@@. The default value is 1. You can set it to a value of your choice. You can change the value of a config key via @@Options -> Config Editor@@. Information on how to use a config editor is given [[https://www.papercut.com/products/ng/manual/sys-mgmt-config-editor.html| here]].

Changed lines 198-200 from:
A: Yes, you can enforce a minimum length by changing the value of the config key "user.card-id-min-length". The default value is 1. You can set it to a value of your choice. ou can change the value of a config key via @@Options -> Config Editor@@. Information on how to use a config editor is given [[https://www.papercut.com/products/ng/manual/sys-mgmt-config-editor.html| here]].

to:
A: Yes, you can enforce a minimum length by changing the value of the config key @@user.card-id-min-length@@. The default value is 1. You can set it to a value of your choice. ou can change the value of a config key via @@Options -> Config Editor@@. Information on how to use a config editor is given [[https://www.papercut.com/products/ng/manual/sys-mgmt-config-editor.html| here]].

Changed lines 196-197 from:
Q: Is there a way to set enforce a minimum length for the card number?
to:
Q: Is there a way to enforce a minimum length for the card number?
Changed lines 198-200 from:
A: Yes you can enforce minimum length of the card number by setting the value of this config key "user.card-id-min-length". The default value is 1. You can set it to a value of your choice. ou can change the value of a config key via @@Options -> Config Editor@@. Information on how to use a config editor is given [[https://www.papercut.com/products/ng/manual/sys-mgmt-config-editor.html| here]].

to:
A: Yes, you can enforce a minimum length by changing the value of the config key "user.card-id-min-length". The default value is 1. You can set it to a value of your choice. ou can change the value of a config key via @@Options -> Config Editor@@. Information on how to use a config editor is given [[https://www.papercut.com/products/ng/manual/sys-mgmt-config-editor.html| here]].

Changed lines 196-200 from:
to:
Q: Is there a way to set enforce a minimum length for the card number?

A: Yes you can enforce minimum length of the card number by setting the value of this config key "user.card-id-min-length". The default value is 1. You can set it to a value of your choice. ou can change the value of a config key via @@Options -> Config Editor@@. Information on how to use a config editor is given [[https://www.papercut.com/products/ng/manual/sys-mgmt-config-editor.html| here]].

January 29, 2013, at 03:36 PM by rick - added an A to my card reader is not work.
Changed lines 182-183 from:
A: (Kent and Jason to contribute)
to:
A: Make sure that the MFD works without the card reader by using a different authentication method. Once you have verified that you can authenticate to the device, swap the reader, MFD or user to see if the problem can be isolated.  If you are still not able to get it working, contact the card reader supplier or PaperCut Support with the steps that you have followed.
Changed line 200 from:
[-Keywords: nfc -]
to:
[-Keywords: nfc, near field communication, near field card, proximity reader, copier authentication -]
Changed lines 3-4 from:
''Note: This KB article is a work in progress and is not yet complete''
to:
''Note: This KB article is a work in progress. Please excuse any typo's''
Changed lines 155-156 from:
->Resellers will find more information in the embedded manual chapter titled "Configuring Swipe Card Readers".
to:
-->Resellers will find more information in the embedded manual chapter titled "Configuring Swipe Card Readers".
Changed lines 186-187 from:
A: (data dots on non clashing frequency or a multi-reader - these can be expensive and maybe slow too - testing recommended before a large purchase, mifare stickers to make all cards the same?)
to:
A: This situation may occur when organizations merge, or on sites where their are multiple security solutions for door access.  Typically a card of one time can't be reader by a reader designed for a card of another type.  There are a number of ''multi-readers'' on the market and in some cases these pose as an acceptable solution.  Some factors which have precluded the use of a multi-reader in the past are:
* Multi-readers are more expensive. It may be a viable solution for small deployments, however can get quite expensive in organizations with large MFD fleets.
* Some multi-readers are quite slow at reading as they need to scan a wider frequency range.

An alternate and popular option is "duel frequency" the cards using RFID data dots (RFID ID stickers
).  Rather than using a multi-reader a single reader type is selected and cards not compatible with this reader have a data-dot sticker applied.  Care needs to be taken to ensure the data dotes selected don't clash with the physical cards.  We recommend careful testing to validate your selection prior to production deployment.
Deleted lines 196-198:

(Cross link this page in various locations)

Changed lines 146-147 from:
->Most card readers have the ability to be reconfigured to read in different formats. Refer to the utilities and manuals provided by your card reader manufacturer.
to:
-->Most card readers have the ability to be reconfigured to read in different formats. Refer to the utilities and manuals provided by your card reader manufacturer.
Changed lines 149-154 from:
->If you just want to use a subsection of the card number as an identifier you can use regular expressions to define which part of the card number is the identifier. This can done in the advanced configuration page; either globally, or for the specific device you wish to configure. Set the ext-device.card-no-regex key to the regular expression you need.

->Example: You have a batch of cards that start with the same value, with only the last 4 digits being the unique identifier. Eg @@1234-5677-1268@@, @@1234-5677-1363@@, @@1234-5677-9992@@

->An appropriate regex would be: @@\d*-\d*-(\d)*@@
to:
-->If you just want to use a subsection of the card number as an identifier you can use regular expressions to define which part of the card number is the identifier. This can done in the advanced configuration page; either globally, or for the specific device you wish to configure. Set the ext-device.card-no-regex key to the regular expression you need.

-->Example: You have a batch of cards that start with the same value, with only the last 4 digits being the unique identifier. Eg @@1234-5677-1268@@, @@1234-5677-1363@@, @@1234-5677-9992@@

-->An appropriate regex would be: @@\d*-\d*-(\d)*@@
Changed lines 158-163 from:
->If you have many card readers that are reading incorrectly it may be easier to configure PaperCut to convert the card number to a different format. PaperCut comes with a number of pre-built converters for common operations such as hexidecimal to decimal, decimal to hexidecimal and ascii encoding converters. For the more advanced use cases you can write your own converter in JavaScript.

->Example: Card is being read in hexidecimal format (@@946EBD28@@), but your records are kept in decimal (@@2490285352@@). Activating the hex2dec converter would make PaperCut do the conversion from hexidecimal to decimal.

->Resellers will find more information in the embedded manual chapter titled "Configuring Swipe Card Readers".
to:
-->If you have many card readers that are reading incorrectly it may be easier to configure PaperCut to convert the card number to a different format. PaperCut comes with a number of pre-built converters for common operations such as hexidecimal to decimal, decimal to hexidecimal and ascii encoding converters. For the more advanced use cases you can write your own converter in JavaScript.

-->Example: Card is being read in hexidecimal format (@@946EBD28@@), but your records are kept in decimal (@@2490285352@@). Activating the hex2dec converter would make PaperCut do the conversion from hexidecimal to decimal.

-->Resellers will find more information in the embedded manual chapter titled "Configuring Swipe Card Readers".
Changed lines 145-149 from:
->'''Option 1: Hardware''' Re-program the card reader
Most card readers have the ability to be reconfigured to read in different formats. Refer to the utilities and manuals provided by your card reader manufacturer.

->'''Option 2: Software''' If you just want to use a subsection of the card number as an identifier you can use regular expressions to define which part of the card number is the identifier. This can done in the advanced configuration page; either globally, or for the specific device you wish to configure. Set the ext-device.card-no-regex key to the regular expression you need.
to:
->'''Option 1: Hardware''' (Re-program the card reader)
->
Most card readers have the ability to be reconfigured to read in different formats. Refer to the utilities and manuals provided by your card reader manufacturer.

->'''Option 2: Software''' (Regex settings inside PaperCut)
->
If you just want to use a subsection of the card number as an identifier you can use regular expressions to define which part of the card number is the identifier. This can done in the advanced configuration page; either globally, or for the specific device you wish to configure. Set the ext-device.card-no-regex key to the regular expression you need.
Changed lines 157-158 from:
->'''Option 3: Software''' If you have many card readers that are reading incorrectly it may be easier to configure PaperCut to convert the card number to a different format. PaperCut comes witha number of prebuilt convertors for common operations such as hexidecimal to decimal, decimal to hexidecimal and ascii encoding converters. For the more advanced use cases you can write your own converter in JavaScript.
to:
->'''Option 3: Software''' (filter/converter settings inside PaperCut)
->If you have many card readers that are reading incorrectly it may be easier
to configure PaperCut to convert the card number to a different format. PaperCut comes with a number of pre-built converters for common operations such as hexidecimal to decimal, decimal to hexidecimal and ascii encoding converters. For the more advanced use cases you can write your own converter in JavaScript.
Changed lines 162-163 from:
Resellers will find more information in the embedded manual chapter titled "Configuring Swipe Card Readers".
to:
->Resellers will find more information in the embedded manual chapter titled "Configuring Swipe Card Readers".
Changed lines 122-123 from:
A: The simplest method is to directly attach a card reader to the device with epoxy resin, however in educational environments a more permanent, tamper-proof approach is called for, and many devices provide a cavity for this purpose. Alternatively a card reader may be mounted within the MFD itself.  If mounting internally - where space is at a premium, it's a good idea to remove the card reader's protective case - this calls for a qualified technician, of course.  Ensure to mount the reader behind a prominent flat surface. 
to:
A: The simplest method is to directly attach a card reader to the device with double-sided tape, or 5 minute epoxy resin, however in educational environments a more permanent, tamper-proof approach is called for, and many devices provide a cavity for this purpose. Alternatively a card reader may be mounted within the MFD itself.  A common internal mounting option is to double-sided tape in the reader inside the scanner feeder hopper on the copier's lift lid (note: some minor disassembly will be required if mounting inside the feeder, and PaperCut recommends that this only be performed by a certified copier technician or a PaperCut certified ASC).  If mounting internally, where space is at a premium, it may be necessary to remove the card reader's protective case.  Ensure to mount the reader behind a prominent flat surface. 
Changed lines 137-138 from:
A small number or card readers do not support keyboard emulation at all (software wanting to support these card readers must build-in support for their specific driver).
to:
A small number or card readers do not support keyboard emulation at all (software wanting to support these card readers must build-in support for their specific driver).  Where possible PaperCut's embedded solutions aim to support a wide array of readers. Internally PaperCut's embedded software includes a number of 'drivers' and will auto-detect as appropriate.
Changed lines 143-145 from:
If you find the your card readers are not reading the correct number then you need to either reconfigure PaperCut or the card reader hardware. Hardware configuration is ideal if you only have a small amount of devices to update (see option 1). The process is different for each card reader manufacturer, and you will need physical access to the device as well as the configuration software that the manufacterer provides. Alternatively, if you have many devices then it may be quicker to configure the card number format conversion in "software" - that is in PaperCut itself.

''Option 1: Hardware'' Re-program the card reader
to:
If you find the your card readers are not reading the correct number then you need to either reconfigure PaperCut or the card reader hardware. Hardware configuration is ideal if you only have a small amount of devices to update (see option 1). The process is different for each card reader manufacturer, and you will need physical access to the device as well as the configuration software that the manufacturer provides. Alternatively, if you have many devices then it may be quicker to configure the card number format conversion in "software" - that is in PaperCut itself.

->'''Option 1: Hardware''' Re-program the card reader
Changed lines 148-154 from:
''Option 2: Software'' If you just want to use a subsection of the card number as an identifier you can use regular expressions to define which part of the card number is the identifier. This can done in the advanced configuration page; either globally, or for the specific device you wish to configure. Set the ext-device.card-no-regex key to the regular expression you need.

Example:
You have a batch of cards that start with the same value, with only the last 4 digits being the unique identifier. Eg @@1234-5677-1268@@, @@1234-5677-1363@@, @@1234-5677-9992@@

An appropriate regex would be: @@\d*-\d*-(\d)*@@
to:
->'''Option 2: Software''' If you just want to use a subsection of the card number as an identifier you can use regular expressions to define which part of the card number is the identifier. This can done in the advanced configuration page; either globally, or for the specific device you wish to configure. Set the ext-device.card-no-regex key to the regular expression you need.

->Example: You have a batch of cards that start with the same value, with only the last 4 digits being the unique identifier. Eg @@1234-5677-1268@@, @@1234-5677-1363@@, @@1234-5677-9992@@

->An appropriate regex would be: @@\d*-\d*-(\d)*@@

->Resellers will find more information in the embedded manual chapter titled "Configuring Swipe Card Readers".

->'''Option 3: Software''' If you have many card readers that are reading incorrectly it may be easier to configure PaperCut to convert the card number to a different format. PaperCut comes witha number of prebuilt convertors for common operations such as hexidecimal to decimal, decimal to hexidecimal and ascii encoding converters. For the more advanced use cases you can write your own converter in JavaScript.

->Example: Card is being read in hexidecimal format (@@946EBD28@@), but your records are kept in decimal (@@2490285352@@). Activating the hex2dec converter would make PaperCut do the conversion from hexidecimal to decimal.

Deleted lines 161-167:
''Option 3: Software'' If you have many card readers that are reading incorrectly it may be easier to configure PaperCut to convert the card number to a different format. PaperCut comes witha number of prebuilt convertors for common operations such as hexidecimal to decimal, decimal to hexidecimal and ascii encoding converters. For the more advanced use cases you can write your own converter in JavaScript.

Example:
Card is being read in hexidecimal format (@@946EBD28@@), but your records are kept in decimal (@@2490285352@@). Activating the hex2dec converter would make PaperCut do the conversion from hexidecimal to decimal.

Resellers will find more information in the embedded manual chapter titled "Configuring Swipe Card Readers".

Changed line 90 from:
# By importing the numbers from a text file.
to:
# By importing the numbers from a [[https://www.papercut.com/products/ng/manual/ch-user-mgmt-import-update.html|text file]].
Changed lines 105-106 from:
A: Normally customers obtain card readers at the same time as they make arrangements to install devices from their hardware supplier. Please note that the card reader hardware required can depend on the multi function devices being used, as some manufacture only support their own proprietary card solutions.
to:
A: Normally customers obtain card readers at the same time as they make arrangements to install devices from their hardware supplier. Please note that the card reader hardware required can depend on the multi-function devices being used, as some manufacture only support their own proprietary card solutions.
Added line 89:
# By configuring PaperCut to perform a lookup on an [[https://www.papercut.com/products/ng/manual/ch-user-mgmt-card-db-lookup.html|external database system]] (e.g. a security card system).
Changed line 92 from:
# Using the server-command or web service `APIs.
to:
# Using the [[https://www.papercut.com/products/ng/manual/apdx-tools.html|server-command]] or [[https://www.papercut.com/products/ng/manual/apdx-tools-web-services.html|web service APIs]].
Added lines 95-96:
The common methods are 1 and 2 as these are simplest to implemented and most automated.  If you're using Microsoft Active Directory, a common selection is to re-use the ''pager number'' filed (not many people have pages these days so it's a good choice for a card number store!).
Added lines 75-76:
An common alternative to ''Fast Release'' is [[https://www.papercut.com/products/ng/manual/ch-mobilerelease.html|Mobile Print Release]].  This option provides an alternative to card readers and allows your users to release held print jobs via their mobile smart phone.
Changed lines 54-57 from:
A: (discuss both software and hardware. Mention why you would want to change the output + how self registration often removes the need for this. The mifare spec is probably to blame for this as there is no set info on how a reader will output the unique ID. Elatec output in hex and `RFIDeas output in decimal by default )

To change the output for Elatec
readers you will need a configuration executable and some scripts. Support has 4 pre built scripts to change the output between hex and decimal as well as reversing the output for each format. Contact support@papercut.com and ask for the TWN guide (PDF format) and the TWN resources zip file.
to:
A: Simple card number conversion such as from Hexidecimal to Decimal can be implemented quickly using a number of methods:

#Hardware - reprogramming your card reader
#Software - Using one of the in-built filters in PaperCut such
as [@hex2dec@].

You'll find more information about this in the FAQ question about changing card number formats below, and also in the manuals for the PaperCut embedded solutions.

''Note about Elatec
readers:'' To change the output for Elatec readers you will need a configuration executable and some scripts. Support has four pre-built scripts to change the output between hex and decimal as well as reversing the output for each format. Contact support@papercut.com and ask for the TWN guide (PDF format) and the TWN resources zip file.
Changed lines 18-22 from:
-->A variety of card reader brands and card technologies may be supported.  Common card reader brands include `RFIDeas and Elatec.  Common card reader technologies include magnetic stripe (AKA magstripe, swipe card, magswipe), MIFARE, HID iCLASS, HID Prox, Indala and barcode.

-->The types of card reader supported depends on the platform.  In general, card readers supporting the USB HID specification are supported on most platforms.  PaperCut resellers possess a detailed matrix of platforms and their supported card readers, so contact your PaperCut reseller if you need further information about a particular platform, card reader brand or card technology.

to:
-->A variety of card reader brands and card technologies may be supported.  Common card reader brands include [[http://www.rfideas.com/|RFIDeas]] and [[http://www.elatec-rfid.com/|Elatec]].  Common card reader technologies include magnetic stripe (AKA magstripe, swipe card, magswipe), MIFARE, HID iCLASS, HID Prox, Indala and barcode.

-->The types of card reader supported depends on the copier/MFD platform.  In general, card readers supporting the USB HID specification (e.g. devices that "emulate" a keyboard) are supported on most platforms.  PaperCut resellers possess a detailed matrix of copier brands and their supported card readers, so contact your PaperCut reseller if you need further information about a particular platform, card reader brand or card technology.

Changed lines 24-25 from:
-->Users can authenticate to a [[https://www.papercut.com/tour/print-release-stations/|PaperCut print release station]] using username and password, entering their id number or presenting a card.  Card authentication provides the convenience of less typing.
to:
-->Users can authenticate to a [[https://www.papercut.com/tour/print-release-stations/|PaperCut print release station]] using username and password, entering their id number, or if configured, presenting ''a card''.  Card authentication provides the convenience of less typing.
Changed lines 158-161 from:
Q: I receive an "unidentified card reader type" message on a Ricoh MFD.  What is this?

A: TODO
to:
Q: I receive an "Uncertified USB card reader found" message on a Ricoh MFD.  What is this?

A: The Ricoh platform only supports a limited number of specific card readers. Please refer to the PaperCut Embedded manual for Ricoh (Appendix A) for details.
November 14, 2012, at 12:13 AM by will - Making RFIDeas cases consistent
Changed lines 54-55 from:
A: (discuss both software and hardware. Mention why you would want to change the output + how self registration often removes the need for this. The mifare spec is probably to blame for this as there is no set info on how a reader will output the unique ID. Elatec output in hex and rfideas output in decimal by default )
to:
A: (discuss both software and hardware. Mention why you would want to change the output + how self registration often removes the need for this. The mifare spec is probably to blame for this as there is no set info on how a reader will output the unique ID. Elatec output in hex and `RFIDeas output in decimal by default )
Changed lines 97-98 from:
Specific information about which card readers work is given in the embedded manual for each of our supported solutions and you PaperCut MF reseller can usually assist with with obtaining any necessary hardware. If you are a PaperCut reseller you should contact your PaperCut Authorised Solution Centre or your local supplier (e.g. Local RFIDeas or Elatec supplier)
to:
Specific information about which card readers work is given in the embedded manual for each of our supported solutions and you PaperCut MF reseller can usually assist with with obtaining any necessary hardware. If you are a PaperCut reseller you should contact your PaperCut Authorised Solution Centre or your local supplier (e.g. Local `RFIDeas or Elatec supplier)
Changed lines 97-98 from:
Specific information about which card readers work is given in the embedded manual for each of the our supported solutions and you PaperCut MF reseller can usually assist with with obtaining any necessary hardware. If you are a PaperCut reseller you should contact your PaperCut Authorised Solution Centre or your local supplier (e.g. Local RFIDeas or Elatec supplier)
to:
Specific information about which card readers work is given in the embedded manual for each of our supported solutions and you PaperCut MF reseller can usually assist with with obtaining any necessary hardware. If you are a PaperCut reseller you should contact your PaperCut Authorised Solution Centre or your local supplier (e.g. Local RFIDeas or Elatec supplier)
Changed lines 95-96 from:
A: TODO
to:
A: Normally customers obtain card readers at the same time as they make arrangements to install devices from their hardware supplier. Please note that the card reader hardware required can depend on the multi function devices being used, as some manufacture only support their own proprietary card solutions.

Specific information about which card readers work is given in the embedded manual for each of the our supported solutions and you PaperCut MF reseller can usually assist with with obtaining any necessary hardware. If you are a PaperCut reseller you should contact your PaperCut Authorised Solution Centre or your local supplier (e.g. Local RFIDeas or Elatec supplier)

Changed lines 131-133 from:
If you find the your card readers are not reading the correct number then you need to either reconfigure PaperCut or the card reader hardware. Hardware configuration is ideal if you only have a small amount of devices to update (see option 1). The process is different for each card reader manufacturer, and you will need physical access to the device as well as the configuration software that the manufacterer provides. Alternatively, if you have many devices then it may be quicker to configure PaperCut to handle the card reader output differently.

''Option 1:''
Re-program the card reader
to:
If you find the your card readers are not reading the correct number then you need to either reconfigure PaperCut or the card reader hardware. Hardware configuration is ideal if you only have a small amount of devices to update (see option 1). The process is different for each card reader manufacturer, and you will need physical access to the device as well as the configuration software that the manufacterer provides. Alternatively, if you have many devices then it may be quicker to configure the card number format conversion in "software" - that is in PaperCut itself.

''Option 1: Hardware
'' Re-program the card reader
Changed lines 136-137 from:
''Option 2:'' If you just want to use a subsection of the card number as an identifier you can use regular expressions to define which part of the card number is the identifier. This can done in the advanced configuration page; either globally, or for the specific device you wish to configure. Set the ext-device.card-no-regex key to the regular expression you need.
to:
''Option 2: Software'' If you just want to use a subsection of the card number as an identifier you can use regular expressions to define which part of the card number is the identifier. This can done in the advanced configuration page; either globally, or for the specific device you wish to configure. Set the ext-device.card-no-regex key to the regular expression you need.
Changed lines 145-146 from:
''Option 3:'' If you have many card readers that are reading incorrectly it may be easier to configure PaperCut to convert the card number to a different format. PaperCut comes with hexidecimal to decimal, decimal to hexidecimal and ascii encoding converters. For the more advanced use cases you can write your own converter in javascript.
to:
''Option 3: Software'' If you have many card readers that are reading incorrectly it may be easier to configure PaperCut to convert the card number to a different format. PaperCut comes witha number of prebuilt convertors for common operations such as hexidecimal to decimal, decimal to hexidecimal and ascii encoding converters. For the more advanced use cases you can write your own converter in JavaScript.
October 23, 2012, at 03:16 AM by will - Added card reader faq for card number conversion
Changed lines 127-131 from:

Q: How do I program my card reader (e.g. to change card number reading format).

A: TODO
to:
Q: My card reader is reading numbers in a format different to my records. How can I change the format?

A: Card readers are configured to expect cards to be formatted in a certain way. Sometimes you may be in a position where a card reader is expecting a format that is different to the format your cards are written in. If you're only using cards readers for self-association then there may not be a need to change any configuration; just as long as each card produces a unique number. However, if you have existing user records with card numbers and want those to match the card reader output then you will need to ensure all of your card readers are working as expected.

If you find the your card readers are not reading the correct number then you need to either reconfigure PaperCut or the card reader hardware. Hardware configuration is ideal if you only have a small amount of devices to update (see option 1). The process is different for each card reader manufacturer, and you will need physical access to the device as well as the configuration software that the manufacterer provides. Alternatively, if you have many devices then it may be quicker to configure PaperCut to handle the card reader output differently.

''Option 1:'' Re-program the card reader
Most card readers have the ability to be reconfigured to read in different formats. Refer to the utilities and manuals provided by your card reader manufacturer.

''Option 2:'' If you just want to use a subsection of the card number as an identifier you can use regular expressions to define which part of the card number is the identifier. This can done in the advanced configuration page; either globally, or for the specific device you wish to configure. Set the ext-device.card-no-regex key to the regular expression you need.

Example:
You have a batch of cards that start with the same value, with only the last 4 digits being the unique identifier. Eg @@1234-5677-1268@@, @@1234-5677-1363@@, @@1234-5677-9992@@

An appropriate regex would be: @@\d*-\d*-(\d)*@@

Resellers will find more information in the embedded manual chapter titled "Configuring Swipe Card Readers".

''Option 3:'' If you have many card readers that are reading incorrectly it may be easier to configure PaperCut to convert the card number to a different format. PaperCut comes with hexidecimal to decimal, decimal to hexidecimal and ascii encoding converters. For the more advanced use cases you can write your own converter in javascript.

Example:
Card is being read in hexidecimal format (@@946EBD28@@), but your records are kept in decimal (@@2490285352@@). Activating the hex2dec converter would make PaperCut do the conversion from hexidecimal to decimal.

Resellers will find more information in the embedded manual chapter titled "Configuring Swipe Card Readers".

Added lines 134-137:
A: Contact your nearest [[https://www.papercut.com/contact/asc/|Authorized Solutions Centre]], who will be able to answer any questions you may have, or organize any necessary tests.

Q: I receive an "unidentified card reader type" message on a Ricoh MFD.  What is this?

Deleted lines 139-142:
Q: I receive an "unidentified card reader type" message on a Ricoh MFD.  What is this?

A: TODO

Changed lines 13-14 from:
A: (* summary of matrix, * reference matrix for authoritive list, *release stations)
to:
A: Card readers can be used with PaperCut in a variety of ways.  The following sections explain the different ways card readers can be used and how card reader support is affected.

->'''[[http://www.papercut-mf.com/tour/track-copiers/|MFDs/MFPs and terminals]] for authentication'''
-->When performing copying, scanning or faxing at an MFD with PaperCut, users typically first authenticate by username and password, entering their id number, or presenting their card (authentication support between platforms differs so not all of these options may be available).

-->A variety of card reader brands and card technologies may be supported.  Common card reader brands include `RFIDeas and Elatec.  Common card reader technologies include magnetic stripe (AKA magstripe, swipe card, magswipe), MIFARE, HID iCLASS, HID Prox, Indala and barcode.

-->The types of card reader supported depends on the platform.  In general, card readers supporting the USB HID specification are supported on most platforms.  PaperCut resellers possess a detailed matrix of platforms and their supported card readers, so contact your PaperCut reseller if you need further information about a particular platform, card reader brand or card technology.


->'''PaperCut print release stations for authentication and/or payment'''
-->Users can authenticate to a [[https://www.papercut.com/tour/print-release-stations/|PaperCut print release station]] using username and password, entering their id number or presenting a card.  Card authentication provides the convenience of less typing.

-->Any [[#keyboard-emulating|keyboard emulating card reader]] is supported here.


->'''Workstations for [[https://www.papercut.com/tour/web-cashier/|Web Cashier]] operators to look up users'''
-->PaperCut Web Cashier is a system for charging for arbitrary disbursements (e.g. binding in a print room) and/or entering cash payments.  When selecting a user to charge/credit, the operator may user a username or a card/id number.  Using a card reader here allows the operator to identify a user without having to type in the number, e.g. by asking the user to present their card for identification.

-->Any [[#keyboard-emulating|keyboard emulating card reader]] is supported here.


->'''Workstations for administrators to look up users'''
-->In PaperCut's [[https://www.papercut.com/tour/browser-based-admin/|web-based administrator interface]] administrators may search for a user by username or card/id number.  Administrators may find it helpful to have a card reader attached to quickly find the matching user, e.g. if they are in the process of distributing cards or testing a particular user account that they have the card for.

-->Any [[#keyboard-emulating|keyboard emulating card reader]] is supported here.


->'''Other 3rd party devices for authentication and/or payment'''
-->Other 3rd party devices such as [[http://www.papercut-mf.com/tour/cash-payment-hardware/|payment kiosks]] commonly support card readers.  Consult the hardware supplier for more information.

Added lines 114-115:

[[#keyboard-emulating]]
Changed lines 118-121 from:
A: A keyboard emulating USB card reader is a card reader that acts just like a keyboard by "typing" the card number each time a card is swiped.   These are the most common type of card reader and are available from a variety of manufacturers and card formats.

These readers can be easily tested in any PC without any special drivers. To do this, plug in the card reader, open a text editor application (like Notepad or Word) and then swipe the card. The number of
the card will be typed into the text editor.
to:
A: A keyboard emulating USB card reader is a card reader that acts just like a keyboard by "typing" the card number each time a card is swiped.  Keyboard emulation can be easily tested.  To do this, plug in the card reader, open a text editor application (like Notepad or Word) and then swipe the card.  If the card number appears in the text editor as if it was typed, this card reader is said to be "keyboard emulating".

Keyboard emulation depends on driver support, although
the majority of card readers available support the USB HID specification and do not require any additional drivers or software to enable keyboard emulation (the drivers are typically bundled with the operating system).

Some card readers require specific drivers to enable keyboard emulation.


A small number or card readers do not support keyboard emulation at all (software wanting to support these card readers must build-in support for their specific driver).


Changed lines 80-81 from:
A: TODO
to:
A: The simplest method is to directly attach a card reader to the device with epoxy resin, however in educational environments a more permanent, tamper-proof approach is called for, and many devices provide a cavity for this purpose. Alternatively a card reader may be mounted within the MFD itself.  If mounting internally - where space is at a premium, it's a good idea to remove the card reader's protective case - this calls for a qualified technician, of course.  Ensure to mount the reader behind a prominent flat surface. 

"Swipe Here" stickers marking the card reader's location can be obtained from our [[https://www.papercut.com/kb/Main/MarketingResources|Marketing Resources]] page.

Changed lines 26-27 from:
To change the output for Elatec readers you will need a configuration executable and some scripts. Support has 4 pre built scripts to change the output between hex and decimal as well as reversing the output for each format. Contact support@papercut.com for the scripts and help configuring the readers.
to:
To change the output for Elatec readers you will need a configuration executable and some scripts. Support has 4 pre built scripts to change the output between hex and decimal as well as reversing the output for each format. Contact support@papercut.com and ask for the TWN guide (PDF format) and the TWN resources zip file.
Changed lines 75-77 from:
I have yet to encounter a PaperCut install where anyone has needed to change the sector to read from.

to:
It is not often anyone needed to change the sector to read from as part of a PaperCut install.

Added lines 121-123:

(Cross link this page in various locations)

Changed line 102 from:
A: Toshiba [=MPFs=], both [=eB3=] and [=eBX=] types, support a variety of card readers. Recently, eBX devices have added support for Magtek card readers. A number of things should be checked (as described in the Toshiba Embedded Manual):
to:
A: Toshiba [=MPFs=], both [=eB3=] and [=eBX=] types, support a variety of card readers.  To support a card reader's, it's important that the Toshiba copier is correctly configured. Recently, eBX devices have added support for Magtek card readers. A number of things should be checked (as described in the Toshiba Embedded Manual):
September 19, 2012, at 11:45 PM by tim - edit self-association
Changed lines 19-21 from:
Please do not confuse card self-association with user self registration. User self registration is a less popular feature used in selected scenarios such as large universities offering public access to printing services in a library.

to:
Please do '''not''' confuse card self-association with [[https://www.papercut.com/products/ng/manual/ch-guest-users.html|user self registration]]. User self registration is a less popular feature used in selected scenarios such as large universities offering public access to printing services in a library.

September 19, 2012, at 11:42 PM by tim - edit self-association
Changed lines 17-19 from:
A: Card self-association allows a user to associate their card with their account without needing any administrator assistance. If the admin enables this feature for the MFP device in "Authentication Methods"->"Swipe Card", then when a user with a new card swipes their card in the reader and if the card number is unknown, it will take the user to a screen for entering their username and password. On subsequent card swipes, the user will be logged straight in as their card is now associated.
(Note:  Don't use
card self-association with end-user self registration [link])
to:
A: Card self-association allows a user to associate their card with their account without needing any administrator assistance. If the admin enables this feature for the MFP device in "Authentication Methods"->"Swipe Card", then when a user presents a new card for the first time, they will be taken to a screen for entering their username and password. If the username and password are entered correctly, then the card is linked with their account. On subsequent card swipes, the user will be logged straight in as their card is now associated.

Please do not confuse card self-association with user self registration. User self registration is a less popular feature used in selected scenarios such as large universities offering public access to printing services in a library.


Changed lines 22-23 from:
A: (discuss both software and hardware)
to:
A: (discuss both software and hardware. Mention why you would want to change the output + how self registration often removes the need for this. The mifare spec is probably to blame for this as there is no set info on how a reader will output the unique ID. Elatec output in hex and rfideas output in decimal by default ) 

To change the output for Elatec readers you will need a configuration executable and some scripts. Support has 4 pre built scripts to change the output between hex and decimal as well as reversing the output for each format. Contact support@papercut.com for the scripts and help configuring the readers.

Changed lines 40-41 from:
A: Yes. The same reader types used on most embedded solutions can also be used for ''Fast Release''.  This ensures the maximum level of card compatibility. The two popular readers are [[http://www.elatec-rfid.com/|Elatec]] and [[(http://rfideas.com/products/pcprox_readers/|RFIDeas]].  The standard USB Elatec reader can be turned into an Ethernet/IP networked reader with a simple ''TCP Converter Box''.  In some cases special firmware needs to be loaded onto the reader to support ''Fast Release''.  For example, the specially written firmware for the Elatec reader allows the PaperCut server to send different audible tones and lights on different conditions (e.g. no jobs, unknown card).
to:
A: Yes. The same reader types used on most embedded solutions can also be used for ''Fast Release''.  This ensures the maximum level of card compatibility. The two popular readers are [[http://www.elatec-rfid.com/|Elatec]] and [[(http://rfideas.com/products/pcprox_readers/|RFIDeas]].  The standard USB Elatec reader can be turned into an Ethernet/IP networked reader with a simple ''TCP Converter Box''.  In some cases special firmware needs to be loaded onto the reader to support ''Fast Release''.  For example, the specially written scripts for the Elatec reader allows the PaperCut server to send different audible tones and lights on different conditions (e.g. no jobs, unknown card).

As well as card readers the Elatec TCP converter can also be used with USB keyboards. This can be useful when customers wish to enter in a number to release jobs. Please note not all USB keyboards/Number pads work so please contact support for models we have tested
.
Added lines 67-77:
A: It is down to the reader what information PaperCut readers from a card.
Typically a magnetic strip reader will read data from 1 of 3 tracks on the magnetic strip. Some "multi" track magstrip readers can be config to read data from a specific track if needed. This is configured via a downloaded configuration utility.

Typically a prox reader will read a unique serial number from a card. This is generally what an organisation would want, in reality a PaperCut Admin would not mind what number was read as long as it was unique for each user.
If you wish to read a different sector from a proximity card then it is possible to read other sectors assuming you have a "playback reader". These look and cost much the same as normal card readers but the firmware on the device acts differently.
Playback readers can be programmed using a configuration utility to read certain sectors from a card. Reading other sectors requires you to know an encryption key. Most sectors would be encrypted by whoever created the card (the door access supplier for example) The configuration utility needs to have an encryption key entered into it, so it can read from that sector. Most cards are protected by two keys, A and B. Key A allows a user to read the sector and key B allows you to read and write to the sector. Key A is all you would need in most cases.
I have yet to encounter a PaperCut install where anyone has needed to change the sector to read from.


Q: What is the best way to mount a card reader onto an MFD/Copier/Printer?

Deleted lines 79-82:
Q: What is the best way to mount a card reader onto an MFD/Copier/Printer?

A: TODO

Changed lines 112-113 from:
A: (data dots on non clashing frequency or a multi-reader - these can be expensive and maybe slow too - testing recommended before a large purchase)
to:
A: (data dots on non clashing frequency or a multi-reader - these can be expensive and maybe slow too - testing recommended before a large purchase, mifare stickers to make all cards the same?)
September 19, 2012, at 01:17 PM by matt - fix toshiba qu formatting
Changed lines 90-94 from:
 * The 08 codes and values are set correctly for the type of card reader. The 08 code is different for eBX versus eB3 but both these devices use the same 08 values depending on the card reader type.
 * Check that LDAP card authentication is turned on for the correct PaperCut LDAP server.
 * Ensure that the card reader is connected prior to the MFD boot up.
 * If using an Elatec [=TWN3=] card reader, then it needs to have Toshiba firmware installed on it.
to:
* The 08 codes and values are set correctly for the type of card reader. The 08 code is different for eBX versus eB3 but both these devices use the same 08 values depending on the card reader type.
* Check that LDAP card authentication is turned on for the correct PaperCut LDAP server.
* Ensure that the card reader is connected prior to the MFD boot up.
* If using an Elatec [=TWN3=] card reader, then it needs to have Toshiba firmware installed on it.
September 19, 2012, at 01:16 PM by matt - add keyboard emulating question.
Added lines 71-76:
A: A keyboard emulating USB card reader is a card reader that acts just like a keyboard by "typing" the card number each time a card is swiped.  These are the most common type of card reader and are available from a variety of manufacturers and card formats.

These readers can be easily tested in any PC without any special drivers. To do this, plug in the card reader, open a text editor application (like Notepad or Word) and then swipe the card. The number of the card will be typed into the text editor.

Q: How do I program my card reader (e.g. to change card number reading format).

Deleted lines 78-81:
Q: How do I program my card reader (e.g. to change card number reading format).

A: TODO

September 19, 2012, at 01:11 PM by matt - adding to DB question
Changed lines 44-45 from:
A: TODO
to:
A: PaperCut offers a variety of ways to get card numbers into the PaperCut database, including:
# By automatically importing the number from a field Active Directory or LDAP.
# By importing the numbers from a text file.
# Users can self-associate their card by swiping and entering their username/password on supported MFD and other hardware.
# Using the server-command or web service `APIs.
# By manually entering the card number in the user details page.

For more information see: [[ImportingCardNumbers | Importing card numbers KB]]

Changed lines 55-56 from:
A: We realize that storing your Card IDs in [[https://www.papercut.com/products/ng/manual/ch-sys-mgmt-user-group-sync.html#ch-sys-mgmt-user-imp-card-id|Active Directory]] may not be possible for all situations. In this case you can use an [[https://www.papercut.com/products/ng/manual/ch-user-mgmt-card-db-lookup.html|external database]] to store your Card IDs
to:
A: We realize that storing your Card `IDs in [[https://www.papercut.com/products/ng/manual/ch-sys-mgmt-user-group-sync.html#ch-sys-mgmt-user-imp-card-id|Active Directory]] may not be possible for all situations. In this case you can use an [[https://www.papercut.com/products/ng/manual/ch-user-mgmt-card-db-lookup.html|external database]] to store your Card `IDs
Changed lines 78-79 from:
Q: My card reader doesn't work on my Toshiba MFP. Why?
to:
Q: My card reader doesn't work on my Toshiba MFD. Why?
Changed line 83 from:
 * Ensure that the card reader is connected prior to the MFP boot up.
to:
 * Ensure that the card reader is connected prior to the MFD boot up.
Changed line 80 from:
A: Toshiba MPFs, both eB3 and eBX types support a variety of card readers. Recently, eBX devices have added support for Magtek card readers. A number of things should be checked (as described in the Toshiba Embedded Manual):
to:
A: Toshiba [=MPFs=], both [=eB3=] and [=eBX=] types, support a variety of card readers. Recently, eBX devices have added support for Magtek card readers. A number of things should be checked (as described in the Toshiba Embedded Manual):
Changed lines 84-85 from:
 * If using an Elatec TWN3 card reader, then it needs to have Toshiba firmware installed on it.
to:
 * If using an Elatec [=TWN3=] card reader, then it needs to have Toshiba firmware installed on it.
September 19, 2012, at 06:52 AM by tim - add question in regards to Toshiba
Added lines 78-85:
Q: My card reader doesn't work on my Toshiba MFP. Why?

A: Toshiba MPFs, both eB3 and eBX types support a variety of card readers. Recently, eBX devices have added support for Magtek card readers. A number of things should be checked (as described in the Toshiba Embedded Manual):
 * The 08 codes and values are set correctly for the type of card reader. The 08 code is different for eBX versus eB3 but both these devices use the same 08 values depending on the card reader type.
 * Check that LDAP card authentication is turned on for the correct PaperCut LDAP server.
 * Ensure that the card reader is connected prior to the MFP boot up.
 * If using an Elatec TWN3 card reader, then it needs to have Toshiba firmware installed on it.

September 19, 2012, at 06:39 AM by tim - add some text about self association - todo: don't know about "end-user self registration"
Changed lines 17-18 from:
A: (Note:  Don't use card self-association with end-user self registration [link])
to:
A: Card self-association allows a user to associate their card with their account without needing any administrator assistance. If the admin enables this feature for the MFP device in "Authentication Methods"->"Swipe Card", then when a user with a new card swipes their card in the reader and if the card number is unknown, it will take the user to a screen for entering their username and password. On subsequent card swipes, the user will be logged straight in as their card is now associated.
(Note:  Don't use card self-association with end-user self registration [link])
Changed lines 37-38 from:
A: Yes. The same reader types used on most embedded solutions can also be used for ''Fast Release''.  This ensures the maximum level of card compatibility. The two popular readers are [[http://www.elatec-rfid.com/|Elatec]] and [[(http://rfideas.com/products/pcprox_readers/|RFIDeas]].  The standard USB Elatec reader can be turned into a Ethernet/IP networked reader with a simple ''TCP Converter Box''.  In some cases special firmware needs to be loaded onto the reader to support ''Fast Release''.  For example, the specially written firmware for the Elatec reader allows the PaperCut server to send different audible tones and lights on different conditions (e.g. no jobs, unknown card).
to:
A: Yes. The same reader types used on most embedded solutions can also be used for ''Fast Release''.  This ensures the maximum level of card compatibility. The two popular readers are [[http://www.elatec-rfid.com/|Elatec]] and [[(http://rfideas.com/products/pcprox_readers/|RFIDeas]].  The standard USB Elatec reader can be turned into an Ethernet/IP networked reader with a simple ''TCP Converter Box''.  In some cases special firmware needs to be loaded onto the reader to support ''Fast Release''.  For example, the specially written firmware for the Elatec reader allows the PaperCut server to send different audible tones and lights on different conditions (e.g. no jobs, unknown card).
Changed lines 9-10 from:
A: PaperCut supports various card readers in a number of areas such as [[http://www.papercut-mf.com/tour/track-copiers/|controlling access to photocopiers]], providing a quick method of authenticating to a stand alone release station and also with the [[http://www.papercut-mf.com/tour/secure-print-release/#fast-release|PaperCut Fast Release]] product.
to:
A: PaperCut supports various card readers in a number of areas such as [[http://www.papercut-mf.com/tour/track-copiers/|controlling access to photocopiers]], providing a quick method of authenticating to a stand alone release station and also being used with the [[http://www.papercut-mf.com/tour/secure-print-release/#fast-release|PaperCut Fast Release]] product.
Changed lines 5-6 from:
This KB article comes common questions (and FAQ) about card readers and their use with PaperCut for photocopier access control and secure print release.
to:
This KB article covers common questions (and FAQ) about card readers and their use with PaperCut for photocopier access control and secure print release.
Changed lines 33-34 from:
Some general information about secure print release can be found here:  http://www.papercut-mf.com/tour/secure-print-release/
to:
Some general information about secure print release can be found [[http://www.papercut-mf.com/tour/secure-print-release/|in the product tour]].
Changed lines 37-38 from:
A: Currently PaperCut only supports the following network card readers for ''Fast Release'' - [[http://www.elatec-rfid.com/|Elatec]] and [[(http://rfideas.com/products/pcprox_readers/|RFIDeas]]. If you have another brand of network card reader, please contact PaperCut support to discuss the options.
to:
A: Yes. The same reader types used on most embedded solutions can also be used for ''Fast Release''.  This ensures the maximum level of card compatibility. The two popular readers are [[http://www.elatec-rfid.com/|Elatec]] and [[(http://rfideas.com/products/pcprox_readers/|RFIDeas]].  The standard USB Elatec reader can be turned into a Ethernet/IP networked reader with a simple ''TCP Converter Box''.  In some cases special firmware needs to be loaded onto the reader to support ''Fast Release''.  For example, the specially written firmware for the Elatec reader allows the PaperCut server to send different audible tones and lights on different conditions (e.g. no jobs, unknown card).

All PaperCut Authorized Solution Centers are able to advise on appropriate technology for a given situation/setup
.
Changed lines 25-26 from:
A: It is a short cut method to release the jobs held in the release queue. It simply releases all held print jobs automatically on login/authentication. It is facilitated by network card readers and has been specifically designed for printers which cannot run embedded software.
to:
A: Fast Release is a short cut method to release the jobs held in a hold/release queue using commodity off-the-shelf card reader hardware (secure print release).  The solution does not rely on embedded software and hence will work with any printer type.  Specifically the solution works as follows:

# The administrator places a networked card reader next to the printer.  The card reader in PaperCut (identified by an IP address) is linked with a queue.
# A user prints to the queue.  The job will not print immediately and will be held.
# The user walks up to the printer and presents their card at the reader.
# The card number is sent to the PaperCut server and the user identified.
# Any jobs in the queue for the adjacent printer (which belong to this user) will automatically start printing.

Some general information about secure print release can be found here:  http://www.papercut-mf.com/tour/secure-print-release/

Changed lines 9-10 from:
A: TODO
to:
A: PaperCut supports various card readers in a number of areas such as [[http://www.papercut-mf.com/tour/track-copiers/|controlling access to photocopiers]], providing a quick method of authenticating to a stand alone release station and also with the [[http://www.papercut-mf.com/tour/secure-print-release/#fast-release|PaperCut Fast Release]] product.
Added lines 37-40:
A: We realize that storing your Card IDs in [[https://www.papercut.com/products/ng/manual/ch-sys-mgmt-user-group-sync.html#ch-sys-mgmt-user-imp-card-id|Active Directory]] may not be possible for all situations. In this case you can use an [[https://www.papercut.com/products/ng/manual/ch-user-mgmt-card-db-lookup.html|external database]] to store your Card IDs

Q: Where can I purchase card reader hardware compatible with my device?

Deleted lines 42-45:
Q: Where can I purchase card reader hardware compatible with my device?

A: TODO

Changed lines 29-30 from:
A: Currently PaperCut only supports the following network card readers - [[http://www.elatec-rfid.com/|Elatec]] and [[(http://rfideas.com/products/pcprox_readers/|RFIDeas]]. If you have another brand of network card reader, please contact PaperCut support to discuss the options.
to:
A: Currently PaperCut only supports the following network card readers for ''Fast Release'' - [[http://www.elatec-rfid.com/|Elatec]] and [[(http://rfideas.com/products/pcprox_readers/|RFIDeas]]. If you have another brand of network card reader, please contact PaperCut support to discuss the options.
Changed lines 25-26 from:
A: It is a short cut method to release the jobs held in the release queue. It simply releases all held print jobs automatically on login/authentication.
to:
A: It is a short cut method to release the jobs held in the release queue. It simply releases all held print jobs automatically on login/authentication. It is facilitated by network card readers and has been specifically designed for printers which cannot run embedded software.
Changed lines 29-30 from:
A: Currently PaperCut supports the following network card readers - [[http://www.elatec-rfid.com/|Elatec]] and [[(http://rfideas.com/products/pcprox_readers/|RFIDeas]]. If you have another brand of network card reader, please contact PaperCut support to discuss the options.
to:
A: Currently PaperCut only supports the following network card readers - [[http://www.elatec-rfid.com/|Elatec]] and [[(http://rfideas.com/products/pcprox_readers/|RFIDeas]]. If you have another brand of network card reader, please contact PaperCut support to discuss the options.
Changed lines 29-30 from:
A: Currently PaperCut supports the following network card readers - Elatec and RFIDeas. If you have another brand of network card reader, please contact PaperCut support to discuss the options.
to:
A: Currently PaperCut supports the following network card readers - [[http://www.elatec-rfid.com/|Elatec]] and [[(http://rfideas.com/products/pcprox_readers/|RFIDeas]]. If you have another brand of network card reader, please contact PaperCut support to discuss the options.
Changed lines 29-30 from:
A:
to:
A: Currently PaperCut supports the following network card readers - Elatec and RFIDeas. If you have another brand of network card reader, please contact PaperCut support to discuss the options.
Changed lines 25-26 from:
A: It is a short cut method to release the jobs held in the release queue. It simply releases all print jobs to be automatically on login/authentication.
to:
A: It is a short cut method to release the jobs held in the release queue. It simply releases all held print jobs automatically on login/authentication.
Changed lines 25-26 from:
A: TODO
to:
A: It is a short cut method to release the jobs held in the release queue. It simply releases all print jobs to be automatically on login/authentication.
Changed lines 29-30 from:
A:
to:
A: 
Changed line 81 from:
''Categories:'' [[Category.GeneralQuestions|+]], [[Category.Cards|+]]
to:
''Categories:'' [[Category.PaperCutMF|+]]
Changed lines 9-10 from:
A:
to:
A: TODO
Changed lines 25-28 from:
A:

Q: Does ''Fast Release'' use the same reader type as those used on MFDs?
to:
A: TODO

Q: Does ''Fast Release'' use the same reader type as those used on `MFDs?
Changed lines 33-34 from:
A:
to:
A: TODO
Changed lines 37-38 from:
A:
to:
A: TODO
Changed lines 41-42 from:
A:
to:
A: TODO
Changed lines 45-46 from:
A:
to:
A: TODO
Changed lines 49-50 from:
A:
to:
A: TODO
Changed lines 53-54 from:
A:
to:
A: TODO
Changed lines 57-58 from:
A:
to:
A: TODO
Changed lines 61-62 from:
A:
to:
A: TODO
Changed lines 65-66 from:
A:
to:
A: TODO
Added lines 1-83:
(:title Common Questions about Card Readers:)

''Note: This KB article is a work in progress and is not yet complete''

This KB article comes common questions (and FAQ) about card readers and their use with PaperCut for photocopier access control and secure print release.

Q: Where are card readers used?

A:

Q: What type of card readers and card standards/formats are supported by PaperCut?

A: (* summary of matrix, * reference matrix for authoritive list, *release stations)

Q: What is card self-association?

A: (Note:  Don't use card self-association with end-user self registration [link])

Q: How can I change the number format read from the card? (e.g. Hexadecimal to Decimal)

A: (discuss both software and hardware)

Q: What is ''Fast Release''?

A:

Q: Does ''Fast Release'' use the same reader type as those used on MFDs?

A:

Q: How do I get my card numbers into PaperCut's database?

A:

Q: My card numbers are in a Database. How can I use this data?

A:

Q: Where can I purchase card reader hardware compatible with my device?

A:

Q: Which track/sector does PaperCut use on a card (e.g. a Magnetic strip card)

A:

Q: What is the best way to mount a card reader onto an MFD/Copier/Printer?

A:

Q: What is a "keyboard emulating" USB card reader?

A:

Q: How do I program my card reader (e.g. to change card number reading format).

A:

Q: I'd like to see if my card format can be read by a reader. How do I get it tested?

A:

Q: I receive an "unidentified card reader type" message on a Ricoh MFD.  What is this?

A:

Q: My card reader is not working.  Can you suggest some trouble-shooting steps?

A: (Kent and Jason to contribute)

Q: I have mixed card types on my network.  What are the options?

A: (data dots on non clashing frequency or a multi-reader - these can be expensive and maybe slow too - testing recommended before a large purchase)

Q: What is two-factor authentication (Card + PIN)?

A: Two factor authentication means "something you know" and "something you have".  For PaperCut and card authentication this means turning on Card + PIN authentication (Card - you have, PIN - only you know).


----
''Categories:'' [[Category.GeneralQuestions|+]], [[Category.Cards|+]]
----
[-Keywords: nfc -]

Comments

Share your findings and experience with other PaperCut users. Feel free to add comments and suggestions about this Knowledge Base article. Please don't use this for support requests.

Article last modified on July 12, 2018, at 12:01 AM
Printable View   |   Article History   |   Edit Article