This document discusses the PrepEID solution which allows event visitors to pay electronically using their eID cards. It proposes a client-server architecture with an API and database on the server side. The demo shows a card reader interacting with the client-side software. The server-side uses ASP.NET, SQL Server, and authentication tokens. Future plans include expanded hosting options and statistics. Testing used a hypervisor with redundant VMs and networks. The goals of traceability and statistics for organizers were largely met through teamwork in developing the client and server software.

1. PrepEID
Stephen D’Hooge
Maarten Vanden Branden 3ICT
Pieter Van Laere

2. Contents
• Current situation
• Solution
• Demo
• Clientside
• Serverside
• Test setup
• Future
• Conclusion
2

3. Current situation
• Event visitors
o Pay with cash
-or-
o Buy tokens
• Event organisators
o Count cash & remaining stock
o No statistics 3

4. Solution
• Client-Server architecture
o Client: web site vs. application
• Privacy
• Secure data traffic (HTTPS)
• Assurance of accessibility
• Added value
o Organisation
o Visitor 4

5. Scheme (simplified)
Conceptual networking scheme 5

6. Demo
by Maarten
6

7. Clientside
• eID SDK
• Middleware
• Card readers
o Developer vs. production quality
Card reader used for development

8. Clientside (2)
• Security levels
o Different passwords
• Local backup functionality Client on startup
8

9. Serverside
• API
• Database
• (Hosting)
9

10. Serverside: API
• ASP.NET MVC4
• REST basic principles
• Connection with database
o MS SQL server
o Redundancy
10

11. Serverside: API (2)
• Authentication
o Credentials
o Different authentication-levels
o Token (encrypted)
 Level
 Event ID
Authentication scheme
Authentication levels 11

12. Serverside: Database
Database diagram
12

13. Test setup
• Hypervisor
• 2 VMs per physical server possible
• 2 separate networks
o Storage
o Management
• Redundancy SQL Server & IIS
o Windows Server Failover Cluster
13

14. Test setup (2)
14

15. Future
• Hosting/Self-hosted
• Website
• Extend statistics
• Independant system
• Inform organisers and visitors
15

16. Conclusion
• Goals mostly realised
• Teamwork
o Client
o Server
o Redundancy
• Meetings every 2 weeks
• Planning about right
16

17. Questions?
17