A SECURED SERVICEORIENTED ARCHITECTURE FOR EGOVERNMENT IN TUNISIA

1
A SECURED SERVICE-ORIENTED ARCHITECTURE FOR
E-GOVERNMENT IN TUNISIA

• Mohamed Sellami
• (mohamed.sellami_at_gmx.net)
• ReDCAD research Unit
• University of Sfax, Tunisia

2
Motivation

• In Tunisia, the majority of e-government projects
  are limited to an informative goal
• Some projects offer services (eg E-CNSS,
  e-CNRPS)
• Simple services (following-up a file )
• No interactions with other administrations

3
Motivation

• Currently in Tunisia

Information or simple service
Web application
5
6
4
Complicated service
1
2
7
10
3
9
8
4
Motivation

• Weak exploitation of the available technologies
  for the treatment and the communication of
  information
• An easy access to information
• A fast response to citizens requests
• An easy and fast achievement of services
• G2G co-operation
• ?The design of an architecture for the
  e-government applications in
  Tunisia

5
Objectif

• An architecture for e-government applications
• Offers on-line services
• Propose reusable services
• Automate the offered services to the maximum
• Support the co-operation between government
  administrations
• Aware of the Tunisian context
• Ensure the safety of information

6
Steps

• Study of the principal requirements of the
  e-governments applications relative to the
  Tunisian case
• Design of a generic architecture for e-government
  in Tunisia
• Validation of the architecture by the
  implementation of an application

7
Plan

• The Tunisian e-government requirements
• Presentation of the proposed architecture
• Case study
• Conclusions

8
The Tunisian e-government requirements
9
Citizens requirements

• Tunisian context
• RTc1 Multiple access channels.
• RTc2 On-line information and services
• RTc3 Privacy Constraint
• Security
• Rsec1 Authenticity of the e-government
  application
• Rsec2 Data confidentiality
• Rsec3 An acquittal

10
Administrations requirements

• Co-operation
• Rcoop Interoperability
• Tunisian context
• RTc4 Data Restriction
• Security
• Rsec4 Filtered services access
• Rsec5 Citizen authentication
• Rsec6 Administration authentication
• Rsec7 Requests integrity
• Rsec8 Data confidentiality

11
proposed architecture Presentation
12
The proposed architecture

• multi-tier architecture
• Integration of existing application
• Easy extension
• Service Oriented Architecture
• Interoperability (Rcoop)
• Composed services

13
Client Layer

• Heavy and light client

• HTTPS Communication
• Encryption (Rsec2)
• Authentification (Rsec1)

ltSOAP-ENVEnvelopegt    ltSOAP-ENVBodygt        lts
TestCNSSgt            lt!Données
personelles--gt         lt/sTestCNSSgt    lt/SOAP-E
NVBodygtlt/SOAP-ENVEnvelopegt
ltSOAP-ENVEnvelopegt    ltSOAP-ENVBodygt        lts
TestCNSSgt            lt!B457V645B45........
-gt         lt/sTestCNSSgt    lt/SOAP-ENVBodygtlt/S
OAP-ENVEnvelopegt
WS-Security

• Communication
• SOAP over HTTP
• WS-Security (Rsec2)

14
Presentation Layer
Login/password
Données
Données
ltSOAP-ENVEnvelopegt    ltSOAP-ENVBodygt        lts
TestCNSSgt            lt!Données........
-gt         lt/sTestCNSSgt    lt/SOAP-ENVBodygtlt/S
OAP-ENVEnvelopegt

• Manages the presentation of the user interface

• Authenticator manages the citizen authentication
  (Rsec5)

• Forwarder treats the information emitted and
  received by the client layer

• Separation of this layer from the application
  layer (RTc1)

OK

• The data itinerary (RTc3)

15
Application Layer

• The orchestration engine(RTc2)
• The application server
• Web services
• Generic Web services
• Digital Signature (Rsec3)
• Authentication (Rsec4)

Composed Service Authentication Service Service
15/31
16
Data Layer

• Ensures the governmental administration data
  storage and persistence
• Lodges the Web services event journals
• Security
• Firewall (Rsec8)
• Authentication

17
Administration Layer

• Follow-up console
• Follow-up of services
• Digital signature checking
• The switches of the Web services (RTc4)

18
Web services with switches
trace
requête
réponse
trace
requête
Exécuter requête
réponse
19
Case study
20
Undertaking a parent
1
, 9
3
2
4
CNRPS Office
8
CNSS Office
5
7
6
takes much time and requires much moving
Tax Office
Municipality
? e-government application based on our suggested
architecture
21
Undertaking a parent
22
Undertaking a parent
CNSS
CNSS
Tax office
CNRPS
CNRPS
municipality
CNSS
23
Undertaking a parent
Digitally signed acquittal
24
Undertaking a parent
From the Administration side
Service data
Data Base
Acquittal
25
Conclusions
26
Conclusions

• A secured service-oriented architecture for
  e-government
• Supports co-operation between government agencies
• Suits the Tunisian context
• Ensures the information safety
• Use of the Web services technology for the
  implementation of this architecture
• Advantages
• Saving time
• Money profit