The website has become one of the primary channels for parliaments to communicate, share information and engage with the public. Today, the proliferation of mobile devices, the social web and higher bandwidth capabilities mean that websites increasingly include audio, video, data, are more interactive and are designed to work cleanly on a wide range of devices. This increases the complexity of planning, managing and resourcing a parliament’s web-estate, as well as the costs of operating it.

1. World e-Parliament Conference 2016
#eParliament
28-30 June 2016 // Chamber of Deputies of Chile // Valparaiso
Integrating Application
Using Single Sign On (SSO)
Indonesian Parliament

2. Introduction
 House of Representatives
of The Republic of Indonesia
 Secretariat General
– IT Specialist
 Erdinal Hendradjaja
– erdinal@dpr.go.id
 Fariza Emra
– farizaemra@dpr.go.id

3. Indonesian Parliament
IT Users
 560 MPs
 1325 state employees (secretariat)
– 20 Bureaus and 63 Departments
 >4000 external employees (MP’s Staff)
 5000 active users per day (average)
– Incl. guest and press

4. Parliamentary Website
www.dpr.go.id

5. Parliamentary Website
Previous Challenges
 Public demand for data
 Content management
 Centralized in IT department
 Difficult to organize data
 Lack of human resource
 Non update content
Issues:Issues:

6. Parliamentary Website
Previous Challenges
 Custom application for each department needs
 Distributed responsibility
 Content managed by the content owners
 Separate admin panel (web-based application)
Solutions:Solutions:

7. Parliamentary Website
New Challenges
 30+ applications built, and each
application has different credential
 Some users have to remember
many username and password
 Each application has its own authorization
 Username/password forgets request
keep increased day by day
 Very difficult to manage users

8. Single Sign On System
The Idea
 Every user has their own personal
username and password
 Easy to manage user authentication
and authorization
 The username and password should
also apply to other application:
email, cloud, office applications and
network applications

9. Single Sign On System
Implementation
 LDAP as communication protocol
to Active Directory service.
 Using attributes of Active Directory to
manage both authentication and
authorization of every user.
 Web-based application as interface
 Using multiple server for load balance

10. Single Sign On System
Implementation
 Windows Operating System
 Apache Web Server
 Microsoft Exchange and
Windows Active Directory Server
 PHP Web Programing

12. Parliamentary Website
Previous Admin Panel : Centralized

13. Parliamentary Website
Web Portal as an Entrance to the “Single Sign On System”

14. Single Sign On System
Benefits
 Easy to manage users
 Log and track: who did what in which app
 Different role in each app
 Easy to build new app

15. Single Sign On System
Challenges and Future Developments
 Specific spec for external app
 Single point failure on AD server
 Security vulnerable
 SSO for mobile Apps
 Simple Password
Recovery Procedure

16. We are still developing this system to get
better user experience
We are open for any suggestion and
further discussion
Thank you