Multiple Card/ID Numbers for a user

KB Home   |   Multiple Card/ID Numbers for a user

Main.MultipleCardNumbersForUser History

Hide minor edits - Show changes to output

July 11, 2018, at 11:57 PM by Aaron Pouliot - Added category identification
Changed line 31 from:
''Categories:'' [[Category.Users|+]], [[Category.ID Card|+]]
to:
''Categories:'' [[Category.Users|+]], [[Category.Identification|+]]
Changed line 26 from:
   [[https://www.papercut.com/products/ng/manual/ch-user-mgmt-card-db-lookup.html]]
to:
   [[https://www.papercut.com/products/ng/manual/applicationserver/topics/user-card-id.html#user-card-db-lookupl]]
Changed line 11 from:
   [[https://www.papercut.com/products/ng/manual/ch-user-mgmt-card-db-lookup.html]]
to:
   [[https://www.papercut.com/products/ng/manual/applicationserver/topics/user-card-id.html#user-card-db-lookup]]
April 15, 2013, at 12:28 AM by 203.12.22.88 -
Changed lines 3-4 from:
As of PaperCut 13.1, users may have up to two card/ID numbers associated with their account. Prior to this, users could only have a single card/ID number. The solution below is suiteable for sites requiring more than two card/ID numbers. Sites running version 13.0 are encouraged to upgrade in order to take advantage of this new feature.
to:
As of PaperCut 13.1, users may have up to two card/ID numbers associated with their account. Prior to this, users could only have a single card/ID number. The solution below is suitable for sites requiring more than two card/ID numbers. Sites running version 13.0 are encouraged to upgrade in order to take advantage of this new feature.
Changed line 31 from:
''Categories:'' [[Category.Users|+]]
to:
''Categories:'' [[Category.Users|+]], [[Category.ID Card|+]]
Deleted line 33:
Changed lines 3-6 from:
PaperCut has built-in support for storing a single card/ID number for each user. This card/ID number is stored in the database record for the user and is visible and editable on the user's details page. The number can also be automatically imported into the PaperCut from the source AD/LDAP server.

In some situations users may have more than one card type that may be used for authentication, or where a card
is to be used in combination with ID logins. e.g. A user may have an employee number or student number that can be used as an alternative to card or username/password authentication.
to:
As of PaperCut 13.1, users may have up to two card/ID numbers associated with their account. Prior to this, users could only have a single card/ID number. The solution below is suiteable for sites requiring more than two card/ID numbers. Sites running version 13.0 are encouraged to upgrade in order to take advantage of this new feature.

For sites that use version 12 and below, implementing an external database (as detailed below)
is still the recommended method of having multiple cards associated with a user account.

User card/ID numbers are stored in the database record for the user and are visible and editable on the userís details page
. The numbers can also be automatically imported into the PaperCut from the source AD/LDAP server.
In some situations users may have more than two card types that may be used for authentication, or where a card is to be used in combination with ID logins. e.g. A user may have an employee number or student number that can be used as an alternative to card or username/password authentication.
Deleted line 10:
Deleted line 12:
Deleted line 34:
February 04, 2013, at 09:03 AM by 120.148.49.192 -
Changed lines 33-35 from:
[-Keywords: dual cards, multiple cards, multiple ids, multiple card numbers, additional card numbers, separate ID and card numbers, per user, two cards -]

to:
[-Keywords: dual cards, multiple cards, multiple ids, multiple card numbers, additional card numbers, separate ID and card numbers, per user, two cards, multi card, multi -]

Changed lines 33-35 from:
[-Keywords: dual cards, multiple cards, multiple ids, multiple card numbers, additional card numbers, separate ID and card numbers, per user -]

to:
[-Keywords: dual cards, multiple cards, multiple ids, multiple card numbers, additional card numbers, separate ID and card numbers, per user, two cards -]

Changed lines 3-8 from:
PaperCut has support for storing a single card/ID number for each user.  This card/ID number is stored on the database record for the user and is visible and editable on the user's details page.  The number can also be automatically imported into the PaperCut from the source AD/LDAP server.

In some situations it may be useful where user's have more than one card type that may be used for authentication, or where a card is to be used in combination with ID logins.  e.g. A user may have an employee number or student number that can be used as an alternative to card or username/password authentication.

PaperCut's feature
to lookup card numbers from an external database source can be used to allow users to be associated with multiple card numbers.  This feature is documented in the manual here:
to:
PaperCut has built-in support for storing a single card/ID number for each user. This card/ID number is stored in the database record for the user and is visible and editable on the user's details page. The number can also be automatically imported into the PaperCut from the source AD/LDAP server.

In some situations users may have more than one card type that may be used for authentication, or where a card is to be used in combination with ID logins. e.g. A user may have an employee number or student number that can be used as an alternative to card or username/password authentication.

PaperCut has a feature that allows it
to lookup card numbers from an external database source. This can be used to allow users to be associated with multiple card numbers. This feature is documented in the manual here:

Changed lines 14-19 from:
# The card/ID is looked up in PaperCut database. If found, then this is the user authenticated.
# If the card/ID is not found, the lookup in the external database is performed.  This looks up a card number and returns the username of the user that card number is associated with.  If there is a match in the external database this use is authenticated.


Using this is quite straightforward.  All it requires is an external database (like SQL Server, Oracle, [=PostgreSQL=], [=MySQL=], etc), and the creation of a database table that maps card numbers to usernames.  For example, the table might be called @@user_cards@@ and contain two fields, @@card_number@@ and @@user_name@@.  Then the SQL used to perform the lookup would be:
to:
# The card/ID is looked up in PaperCut database. If it is found, then this is the user authenticated.
# If the card/ID is not found, the lookup in the external database is performed.  This looks up a card number and returns the username of the user that card number is associated with.  If there is a match in the external database this user is authenticated.


Using this is quite straightforward.  All it requires is an external database (such as SQL Server, Oracle, [=PostgreSQL=], [=MySQL=], etc), and the creation of a database table that maps card numbers to usernames.  For example, the table might be called @@user_cards@@ and contain two fields, @@card_number@@ and @@user_name@@.  Then the SQL used to perform the lookup would be:
Changed lines 32-34 from:
[-Keywords: dual cards, multiple cards, multiple ids, multiple card numbers, additional card numbers, separate ID and card numbers, per user, -]

to:
[-Keywords: dual cards, multiple cards, multiple ids, multiple card numbers, additional card numbers, separate ID and card numbers, per user -]

Changed lines 32-34 from:
[-Keywords: dual cards, multiple cards, multiple ids, multiple card numbers, separate ID and card numbers-]

to:
[-Keywords: dual cards, multiple cards, multiple ids, multiple card numbers, additional card numbers, separate ID and card numbers, per user,  -]

Added lines 30-31:
''Categories:'' [[Category.Users|+]]
----
Added lines 1-32:
(:title Multiple Card/ID Numbers for a user :)

PaperCut has support for storing a single card/ID number for each user.  This card/ID number is stored on the database record for the user and is visible and editable on the user's details page.  The number can also be automatically imported into the PaperCut from the source AD/LDAP server.

In some situations it may be useful where user's have more than one card type that may be used for authentication, or where a card is to be used in combination with ID logins.  e.g. A user may have an employee number or student number that can be used as an alternative to card or username/password authentication.

PaperCut's feature to lookup card numbers from an external database source can be used to allow users to be associated with multiple card numbers.  This feature is documented in the manual here:

    [[https://www.papercut.com/products/ng/manual/ch-user-mgmt-card-db-lookup.html]]


This lookup feature works as follows when a user authenticates with a card/id:
# The card/ID is looked up in PaperCut database. If found, then this is the user authenticated.
# If the card/ID is not found, the lookup in the external database is performed.  This looks up a card number and returns the username of the user that card number is associated with.  If there is a match in the external database this use is authenticated.


Using this is quite straightforward.  All it requires is an external database (like SQL Server, Oracle, [=PostgreSQL=], [=MySQL=], etc), and the creation of a database table that maps card numbers to usernames.  For example, the table might be called @@user_cards@@ and contain two fields, @@card_number@@ and @@user_name@@.  Then the SQL used to perform the lookup would be:

  @@select user_name from user_cards where card_number = {cardnumber}@@

This table can then be populated with the mapping between users and these card numbers.

For setup instructions see the manual here:

    [[https://www.papercut.com/products/ng/manual/ch-user-mgmt-card-db-lookup.html]]

'''NOTE:''' Like the card numbers in the PaperCut database, you should ensure that the card numbers uniquely identify a single user.  i.e. you should not have a card number map to multiple users.

----
[-Keywords: dual cards, multiple cards, multiple ids, multiple card numbers, separate ID and card numbers-]

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 11, 2018, at 11:57 PM
Printable View   |   Article History   |   Edit Article