Show Advanced KnowledgeHide Advanced Knowledge

digital signed certificates using QR-Codes

1 Initial Problem

The current normal certificates are not signed in any way. A digital signed certificate using certificates is complex and cannot be verified easy or without a dependency to a CRL-list etc. There is no way to check a automatically created certiciate if its genuine, manipulated, revoked or limited.

2 Conceptual Summary

The trainer may add an optional QR-Code to the certificate. This QR-Code contains the link to a website (public or limited access) of ILIAS which contains the important data. It will be printed with a short information text and a serial number for manual verification.

If the certificate has been found this date will be visible i.e.

• learners Name
• Certification Date
• valid until
• trainers name
• Valid Status (valid, revoked, limited etc.)

If no certificate serial number was trasmitted successfully or if he want to verify multiple Certfiicates, the user may enter the serial number manually by enter up to X serials in a form. The result display the validation data as a table.

The user may check now the displayed data against the printed informations on the certificate.

If the certificate has not been found an error message appears, depending on the  cause:

• This certificate has been revoked.
• .... not found ....
• ... is invalid since ..

To offer a website like this, i assume additional data tables needs to be added.

3 User Interface Modifications

3.1 List of Affected Views

• Course - Settings - Certificate (Option to insert the QR Code at a specific position, defined with the distance to the margins.)
• System Administration - Certificates (Option to define the additional text, printed next to the QR-Code)

3.2 User Interface Details

{For each of these views please list all user interface elements that should be modified, added or removed. Please provide the textual appearance of the UI elements and their interactive behaviour.}

3.3 New User Interface Concepts

{If the proposal introduces any completely new user interface elements, please provide a link to separate feature wiki entries for each of them according to the kitchen sink template.}

4 Technical Information

{The maintainer has to provide necessary technical information, e.g. dependencies on other ILIAS components, necessary modifications in general services/architecture, potential security or performance issues.}

5 Contact

• Author of the Request:  Hesse, Joel [Joel_Hesse], [[Parfümerie Douglas GmbH]
  
• Maintainer: {Please add your name before applying for an initial workshop or a Jour Fixe meeting.}
• Implementation of the feature is done by: {The maintainer must add the name of the implementing developer.}

6 Funding

If you are interest in funding this feature, please add your name and institution to this list.

• …

7 Discussion

8 Implementation

{The maintainer has to 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}.