Feature Wiki

Information about planned and released features

Tabs

QR Code to improve the protection against forgery of certificates

1 Requirements

To improve the protection against forgery of ILIAS certificates, it should be possible to add a unique QR code to each certificate, e.g. via a placeholder [QRCODE] in the certificate text.

To make the QR code unique it has to encode

  • the NIC-ID of the ILIAS installation
  • the object ID of the object which issues the certificate
  • the user ID of the owner/recipient of the certificate
  • the timestamp when the certificate was issued

Then, anybody should be able to scan the QR code on the printed certificate to validate its genuineness.

By scanning the QR code a message should be displayed to mark the certificate as valid. The message should contain the most essential information on the certificate. Following an additional link it should be possible to view the original certificate to compare it to the printed one.

Here are two links to organisations which use QR codes to sign their certificates

HIS-QIS implemented a similar process to verify certificates of enrollment by a 16-digit verification number. You can check the validity online using a web form.
The process is described here at the FH Kiel which uses HIS-QIS: http://www.fh-kiel.de/index.php?id=8692 (German)

Here, the process could easily be improved using a QR code which encodes the URL of the mentioned web form giving the verification number as a URL parameter.

One challenge:

The information on issued certificates has to be stored persistently. It should still be possible to validate a QR code on a printed certificate, even if its owner already left the institution (e.g. finished his/her studies and left the university) and his/her ILIAS account was closed and deleted.
The same problem applies when the test object, which issued the certificate, will be deleted (e.g. in the case it belonged to an elderly semester course).

2 Additional Information

  • Idea / concept: Hilbert, Mirco [mirco.hilbert]
  • Interest in funding: (please indicate if you are interested/able to fund this feature)
  • Maintainer: (will be set by Jour Fixe / maintainer)
  • Implementation of the feature is done by (will be set by Jour Fixe / maintainer)
  • Testcases by: (please add your name if you want to create the testcases for this feature)

3 Discussion

4 Implementation

{please give a description of the final implementation and add screenshots if possible}

Test Cases

Test cases completed at {date} by {user}

  • {Test case number linked to Testrail} : {test case title}

Approval

Approved at {date} by {user}.

Last edited: 18. May 2016, 09:41, Hilbert, Mirco [mirco.hilbert]