Building open source identity infrastructures
Download as ODP, PDF4 likes1,287 views
Nowadays most components of a full identity infrastructure are available as Open Source components - and some even within The ASF: identity repositories, provisioning engines, access management systems. Picking these bricks to realize a solution that will suit the wide-range ever-changing organizations' needs is a real challenge for all system integrators in the Identity & Access Management area. Some real-word use cases and scenarios will be reviewed in this presentation to highlight strengths, flexibility and benefits - but also wicked problems and possible improvements - that Open Source Identity infrastructures can provide to organizations and final users.
![[WSO2Con EU 2017] IAM: Catalyst for Digital Transformation](https://cdn.slidesharecdn.com/ss_thumbnails/grzayjflsri5gyiqkf9x-signature-6abac760590306a9c092f3ba66249d9a805ee6b52c9eb804a80eabb33b95c5ef-poli-171106133401-thumbnail.jpg?width=560&fit=bounds)
Ad
More Related Content
What's hot (20)
Viewers also liked (20)
Ad
Similar to Building open source identity infrastructures (20)
Ad
More from Francesco Chicchiriccò (10)
Recently uploaded (20)
Building open source identity infrastructures
- 1. Building Open Source Identity Infrastructures Francesco Chicchiriccò [email protected] https://about.me/ilgrosso Building Open Source Identity Infrastructures Francesco Chicchiriccò [email protected] https://about.me/ilgrosso
- 2. The Identity Management NeedThe Identity Management Need
- 3. Identity Vs Account Source: https://saberhamidi.wordpress.com/2015/02/22/topic-2-should-we-have-more-than-one-online-identity/
- 4. Identity Vs Account • Account • record containing data about a person • technical info needed by the information system for which the account is created and managed • (Digital) Identity • representation of a set of claims made by one digital subject about itself • ...it's you
- 5. Why Identity Management?• Operational costs • Multiple sources of identity data • Manual user provisioning and password reset • Labor-intensive, paper-based approval • Compliance • No record of who has access to which IT resources • Difficult to deprovision access rights upon termination • No complete audit trail available • Hard to prevent unauthorized access
- 8. Identity Technologies • Identity Stores • Storage of user information • Provisioning Engines • Synchronize account data across identity stores and a broad range of data formats, models, meanings and purposes • Access Managers • Security mechanisms that take place when a user is accessing a specific system or functionality
- 9. Identity Store • Examples • LDAP / Active Directory • RDBMS • Meta and Virtual Directories • Accounts can be created and managed in one place only • Each application manages authentication separately • The user may use the same password for all the connected applications
- 10. ...is it enough? • Heterogeneity of systems • Lack of a single source of information • HR for corporate id, Groupware for mail address, ... • Need for a local user database • Inconsistent policies • Lack of workflow management • Hidden infra management cost, growing with organization
- 11. Provisioning Engine • Keeping the identity stores as much synchronized as possible (and practical) • Need to be customizable and flexible • Priority: non-intrusive • Focused on application back-end • Critical: data exchange with identity stores • Connectors • Agents
- 13. Access Manager • Mediator to all access to all applications • Focused on application front-end • Aspects • Authentication • Single SignOn • Authorization (OAuth, XACML, ...) • Federation (SAML, Liberty, ...) • Mainly applicable to web applications • Difficult integration with pre-existing apps
- 16. Gather... • Number and type of identities • Number of roles / groups (and what are they used for) • External resources (all covered by standard connectors?) • Approval workflow(s)? • Self-service? • Which applications to protect? • Which authentication mechanisms? • Which authorization types? ...essentially, shape the identity and access flows
- 17. ...design... • Schema for various identities (users, roles, groups, ...) • Identify mapping for all resources • Not too complex! • Watch roles size to avoid RBAC's role explosion • Don't be tempted to redesign the whole network • Provisioning needs to be flexible • Reduce impact of access management on existing applications • Prioritize requirements
- 18. ...build... • Carefully choose the building blocks • Can't simply buy COTS • On-premises • Proprietary • Open Source • As-a-service • Consider prototyping the designed solution (PoC)
- 19. ...and start again • IAM is a continuous process, not a turn-key project • New applications to protect • New resources to integrate • Identity flows evolution • IAM deliveries frequently fail • Mix of complex and unrelated technologies • Unexpected interactions • Mess with internal processes • Discover Policy Vs Reality
- 20. The Open Source Identity StackThe Open Source Identity Stack
- 21. Open Source IAM • Why? • Flexibility, adaptability and agility • Cost effectiveness • Start small and grow • Solid information security • No vendor lock-in • Caveats • Integration with proprietary software (AD over all) • Enterprise support availability
- 23. Selection Criteria • Open Standards • Design for integration • Well-established • Supported • Alive • ...Open Source!
- 24. The Identity Ecosystem • Triggered by open companies in the Open Source IAM area • Common place for open source players, system integrators and service providers • Ensuring IAM open source components work well together • Easy access to enterprise support providers • Several options for each single component • More at http://www.identity-ecosystem.org/
- 25. Real World Use CasesReal World Use Cases
- 26. Disclaimer I am V.P. Apache Syncope and CEO of Tirasa, providing enterprise support and services for Apache Syncope, so… don't be surprised Syncope is everywhere :-) Disclaimer I am V.P. Apache Syncope and CEO of Tirasa, providing enterprise support and services for Apache Syncope, so… don't be surprised Syncope is everywhere :-)
- 27. #1 Stadtwerke München • One of largest German municipal utilities • Mobile ticketing for public transportation and bike sharing • self-registration • login • password reset • user suspend / reactivate • > 250k registered users • > 80k authentications per day
- 28. #2 Ospedali Riuniti Ancona • University hospital • Active synchronization from HR to Microsoft Active Directory • Centralized provisioning, authentication and authorization of medical record systems • Windows domain SSO • SAML 2.0 federation with regional network • ~ 5000 users
- 29. #3 Stichting Bibliotheek.nl • Dutch foundation that aims to expand and manage the Digital National Library • The IAM infrastructure aims to hold all users of the national library in the Netherlands, fed by a continuous feed from the local libraries • All Dutch library members can authenticate and use digital services connected to the IAM infrastructure • > 8 million users
- 30. #4 University of Milan • Very complex provisioning flows involving • Microsoft Active Directory • OpenLDAP • 3 different RDBMS • Oracle E-Mail Server • ~ 5k employees • > 60k students • ~ 800 roles
- 31. Questions? All text and image content in this document is licensed under the Creative Commons Attribution-Share Alike 3.0 License (unless otherwise specified). Apache, Syncope, Apache Syncope, the Apache feather logo, the Apache Syncope project logo and the Apache Syncope logo are trademarks of The Apache Software Foundation. All other marks mentioned may be trademarks or registered trademarks of their respective owners.