Call for round the year submissions for Rootconf in 2020

Submit a proposal at any time in the year on DevOps, infrastructure security, cloud, and distributed systems. We will find you a suitable opportunity to share your work.

FreeIPA: The swiss army knife of open-source identity management

Submitted by Aditya Kamat (@adityakamat) on May 6, 2019

Section: Full talk Technical level: Intermediate Session type: Demo Status: Submitted


FreeIPA is used in the management of Linux user identities, groups, and passwords centrally with the help of a CLI as well as an easy to use GUI. FreeIPA provides centralized authentication, authorization, and account information for Linux and Unix network environments. It is built on top of well known open-source components like LDAP, KDC, PKI, etc. FreeIPA can seamlessly integrate with an existing Active Directory environment.
In this talk, We will cover the basics of FreeIPA and how to leverage FreeIPA in a production environment and address the concerns of an organization pertaining to compliance, security and risk mitigation.


  • FreeIPA Introduction
  • FreeIPA architecture and components
  • Use cases of FreeIPA in production
  • Demo of FreeIPA
  • Achieving high availability
  • Audit logs

Speaker bio

Aditya Kamat is a Cyber Security enthusiast working in the systems architect team at Endurance International Group. His areas of interest include Linux performance tuning, building resilient and highly scalable systems and participating in CTF competitions. He likes going on treks and long bike rides during the weekends. He has completed his engineering from BMS College of Engineering, Bangalore.


  • Zainab Bawa (@zainabbawa) 12 months ago

    Thanks for the proposal, Aditya. Some comments:

    1. The current proposal is a tool exposition. The approach is generic, in the sense that you are describing what the tool does. Participants can find the same information online, in FreeIPA’s documentation, instead of listening to talk.
    2. To make this more interesting, you have to explain what is the problem that this tool solves and therefore, why pick this. This has to stem from your experience with using the tool for solving a problem at work.
    3. Are there similar tools which solve the same problem? Show comparison, and upsides and downsides of the tools you compare?
    4. Explain how the tool was implemented for your use case.
    5. Show before-after scenario: what was impacted/compromised with using this tool in your use case? How was the problem you were solving better off or worse off when using this tool?

    The current proposal needs work in terms of shaping the idea. Suggest you work on this to the next iteration, so that we can see how well formed this becomes. We can then put it into consideration for Pune/Hyd editions of Rootconf.

Login to leave a comment