DOCSLIB.ORG

Freeipa-Manager

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Freeipa-Manager Masaryk University Faculty of Informatics freeipa-manager Bachelor’s Thesis Kristián Leško Brno, Fall 2019 Masaryk University Faculty of Informatics freeipa-manager Bachelor’s Thesis Kristián Leško Brno, Fall 2019 This is where a copy of the official signed thesis assignment and a copy ofthe Statement of an Author is located in the printed version of the document. Declaration Hereby I declare that this paper is my original authorial work, which I have worked out on my own. All sources, references, and literature used or excerpted during elaboration of this work are properly cited and listed in complete reference to the due source. Kristián Leško Advisor: doc. RNDr. Vlastislav Dohnal, Ph.D. i Acknowledgement My gratitude goes to Michal "Blesk" Marciniszyn, the author of the original idea behind freeipa-manager, and to the rest of our team at GoodData for their patient guidance and support. iii Abstract The goal of this work is to facilitate an improvement in identity man- agement and access control processes in a corporate environment. The thesis implements a tooling for verification and application of access control structures in a FreeIPA server, providing a possibility of clean access rule design and better review and audit options. The implemented software serves for synchronization of access control entities between an authoritative configuration source and the server. iv Keywords FreeIPA, identity management, LDAP, RBAC, access control v Contents Introduction 1 1 Identity management (IdM) 3 1.1 Motivation ..........................3 1.2 Concepts ............................4 2 IdM technologies overview 5 2.1 Directory service .......................5 2.2 LDAP .............................6 2.3 Common IdM solutions ....................6 2.4 Existing solutions evaluation .................8 3 FreeIPA 9 3.1 Features ............................9 3.2 Entity representation ..................... 11 3.3 Usage at GoodData ...................... 12 4 GoodData requirements 15 4.1 Entity structure management ................. 15 4.2 Backup and restore capabilities ................ 16 4.3 Inter-team cooperation .................... 17 4.4 Audit ............................. 18 5 freeipa-manager implementation 19 5.1 Brief history .......................... 19 5.2 Design decisions ....................... 20 5.3 Features ............................ 22 Conclusion 27 Bibliography 29 vii Introduction Identity management and access control are highly important topics in virtually all corporate environments. Various solutions, or com- binations thereof, are utilized by companies, and there are frequent impulses to improve the processes and approaches in these areas. This thesis documents my arrival at one such company where improvement in the practicality of identity management was desired, and the opportunity I was offered to create a solution that would simplify the lives of those managing user access to company resources. The first part of this thesis introduces the problem of identity management as a whole, evaluating the various existing solutions with their advantages and disadvantages. Later, I move on to the specific description of FreeIPA, which is the tool used as part ofthe identity management solution at GoodData, and which serves as the basis for the tooling I have implemented. The fourth chapter then describes the state of affairs at GoodData before the described tooling came to be, the limitations of the FreeIPA software encountered, as well as the painfulness in the specific use cases that became the driving factor for the changes that I was assigned to implement. In chapter five, I elaborate on the tooling I created to tackle the chal- lenges faced by my colleagues responsible for identity management tasks, outlining the challenges encountered during implementation and the deployment process. I then move on to describe the specific changes implemented in the scope of this thesis that further improve the tool and help bring it to a more practical and useful state. The thesis wraps up by recounting the plans for further develop- ment of the tool in the future, along with the skills and experience that I have had the chance to obtain via participation in this project, the largest one entrusted to me to date. 1 1 Identity management (IdM) Identity management (IdM) can be defined as the collection of pro- cesses utilized to grant, verify, and revoke identity representations, or credentials, of users of a computer system [1]. The term computer sys- tem should be understood more broadly in this context; for instance, a system of cards managing users’ access to an office building constitutes an identity management system although it may not be considered a computer system in the intuitive sense. Various environments may call for the need to employ an identity management system, such as user management in a public web ap- plication or access control of employees to different services inside a company. As foreshadowed in the introduction, this thesis will focus on the latter described example, i.e. private identity management in a business context. 1.1 Motivation The most fundamental goal of identity management is to ensure that a system can differentiate its users and provide the appropriate level of access to each of its resources to desired users only. Some small-scale companies may be able to function without an explicit identity management system, allowing each user to access all available resources without any kind of limits or authentication and relying on informal agreements to prevent malicious behavior. However, as the size of a company and the importance of its resources grows, this primitive level of access control (or absence thereof) is not sufficient anymore; the risks that such an approach would cause are not acceptable to most enterprises. Additionally, resources managed by a company may not be limited to a secure perimeter not accessible from outside. External services (e.g., e-mail, version control repository hosting, cloud software, etc.) may be utilized by the company as well; and since virtually all such systems require authentication of users, it follows that identity man- agement on the part of the company is a necessity. 3 1. Identity management (IdM) 1.2 Concepts A vast majority of enterprises adhere to a handful of security princi- ples to ensure adequate protection of their resources from possible damages caused by users, either by negligence or malicious behavior. 1.2.1 Least privilege The principle of least privilege states that each user should only be granted access to systems they necessarily require to carry out their assigned work. The goal is to stop users from damaging the company systems by not granting them extra powers they might abuse [2]. Addi- tionally, the application of this principle may prevent situations where a user might accidentally access and break a system they do not use as part of their work. 1.2.2 Segregation of duties The related concept of segregation of duties is the idea that no single user should possess so much power that abusing it would be detrimental to the company [3]. This implies defining processes such as code review, where each change to the produced software made by one user needs to be verified by another one, or distribution of access to critically important systems to different groups of users. 1.2.3 Role-based access control Closely related to the principles defined above, role-based access control (RBAC) is the idea is that access assigned to every user is based on their role or position inside the company [4]; for instance, there is a predefined set of access rules for a regular user, another setfora manager, another for the director, and so on. In common identity management solutions, this access control paradigm may be implemented using nested user groupings to repre- sent both the top-level user roles and other levels of access granularity. A specific example of such a group structure will be provided later,in Chapter 4. 4 2 IdM technologies overview This chapter presents an overview of industry-standard identity man- agement technologies and their usage in the major IdM deployment solutions. The focus has been placed on solutions with close relevance to the topic of this work due to their technological proximity to FreeIPA or their possible role as target platforms for future expansion of the implemented tool. As FreeIPA itself holds a central role to the theme of this work, a separate following chapter is dedicated to its description and analysis. 2.1 Directory service A directory service, also known as name service, is an application pro- viding the possibility to store and retrieve structured data records. Its concept based on pre-computer era paper telephone directories where one might look for a telephone number based on a person’s name, directory services enable storage and retrieval of resources in a hierarchical structure based on their pre-assigned names. A directory service may be provided by a single server but distributed solutions are most commonly preferred. In the context of identity management, a directory service is gen- erally used to store user records serving as source of truth for authen- tication purposes. Various relevant types of data can be stored in a directory server apart from user information, such as representation of relationships between resources. This allows usage of directory servers for authorization by specifying groupings and access rules between defined resources. Widespread directory service implementations
Load more

Recommended publications
  • Open Directory & Openldap
    Open Directory & OpenLDAP David M. O’Rourke Engineering Manager Overview • Background on Apple’s Open Directory Technology (8 minutes) – What is it – What is Directory Services • How has Apple integrated OpenLDAP (20 minutes or less) – what has Apple added to OpenLDAP? • Questions and Answers (remaining time) Open Directory • Open Directory is a technology name – Covers both client access technologies and server technologies – Integrates and promotes industry standard technologies • Open Directory is built into Mac OS X & Mac OS X Server – Been there since 10.0 • Open Sourced as part of Darwin – http://developer.apple.com/darwin/projects/ opendirectory/ What Is Directory Services • Abstraction API for read/write access to system configuration and management data – Users, groups, mount records and others – Authentication abstraction Mac OS X Software Directory Services NetInfo LDAP BSD Files Other… Directory Services in 10.3 • Includes – LDAPv3 (read/write), Native Active Directory, NetInfo, NIS, BSD/etc files – Service Discovery: Rendezvous, SMB, AppleTalk, and SLP – LDAPv3 client support replication fail over • Documented Access API and plug-in API – SDK posted – Sample code, sample plug-in, notes – Directory Services Headers are installed in – /System/Library/Frameworks/DirectoryService.framework – Command line tool for directory editing ‘dscl’ 10.3 Usage of Directory Services • Login Window uses Directory Services for all user authentication – Managed Desktop • All Security Framework authentication uses Directory Services • Legacy Unix
    [Show full text]
  • AWS Directory Service Setup with Netapp Cloud Volumes Service for AWS Prabu Arjunan, Netapp August 2019
    AWS Directory service setup with NetApp Cloud Volumes Service for AWS Prabu Arjunan, NetApp August 2019 Abstract This document provides instructions to help users set up the AWS directory services environment for using NetApp® Cloud Volumes Service for Amazon Web Services (AWS). TABLE OF CONTENTS 1 Overview ................................................................................................................................................ 3 2 Requirements ........................................................................................................................................ 3 3 Creating the AWS Active Directory service ....................................................................................... 4 4 Adding the Active Directory server to Cloud Volumes Service ..................................................... 10 5 Creating a cloud volume that uses the Active Directory server .................................................... 12 Common errors messages....................................................................................................................... 14 References ................................................................................................................................................. 14 Version History ......................................................................................................................................... 14 2 AWS Directory service setup with NetApp Cloud Volume Service for AWS © 2019 NetApp, Inc. All rights reserved. 1 Overview
    [Show full text]
  • White Paper | September 2 0 1 7
    Oracle Directory Services Buyer’s Guide ORACLE WHITE PAPER | SEPTEMBER 2 0 1 7 Disclaimer The following is intended to outline our general product direction. It is intended for information purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described for Oracle’s products remains at the sole discretion of Oracle. ORACLE DIRECTORY SERVICES – BUYER’S GUIDE Table of Contents Introduction 1 Business Drivers 2 Oracle Directory Services 3 Key Considerations for Some Popular Scenarios 4 Cloud 4 Mobile 4 Customer-Facing Internet 4 Employee-Facing Intranet 5 Directory Services Checklist 5 Conclusion 7 ORACLE DIRECTORY SERVICES – BUYER’S GUIDE Introduction In the late 1990s, directory servers were essentially designed as white-page applications for providing users with secure access to enterprise resources through authentication and authorization processes. Since then, their use has been extended to partners and customers, thus creating the need to support an increasing number of diverse users and communities. Today, directory services need to accommodate hundreds of millions of users and provide additional services to break identity silos. With the ubiquitous use of mobile devices as well as cloud deployments and the integration of social networks identities into the enterprise fabric, billions of objects are transacted everyday through directory services. Modern directory services now go beyond the initial capability to store objects in an identity repository. Directory solutions have evolved around three foundation services: » Storage: Persisting and maintaining entries representing identities.
    [Show full text]
  • The 12 Essential Tasks of Active Directory Domain Services
    WHITE PAPER ACTIVE DIRECTORY DOMAIN SERVICES The 12 Essential Tasks of Active Directory Domain Services Using the right tools and processes helps reduce administrative overhead and ensures directory service is always available By Nelson Ruest and Danielle Ruest Sponsored by WHITE PAPER ACTIVE DIRECTORY DOMAIN SERVICES ABSTRACT Active Directory Domain Services (AD DS) administration and management includes Sponsored by 12 major tasks. These tasks cover a wide breadth of business needs and are not all performed solely by AD DS administrators. In fact, administrators can and should delegate several tasks to other members of their technical community, technicians, help desk personnel, even users such as team managers and administrative assistants. While delegation is a way to reduce the amount of work administrators have to do when managing AD DS infrastructures, it really only addresses one or two of the 12 tasks, for example, user and group administration as well as end point device administration. The other ten tasks can be staggering in nature—security, networked service administration, OU-Specific Management, Group Policy Object management and many more—and because of this can take up inordinate amounts of time. You can rely on Microsoft’s built-in tools to reduce some of this workload, but are the native tools enough? Perhaps it’s time to reduce AD DS administration overhead by automating most tasks and tightening internal security. Address this by first, determining what the twelve essential labors of Active Directory are and then, see how you can reduce AD DS workloads through the implementation of proper management and administration tools.
    [Show full text]
  • [MS-DSSP]: Directory Services Setup Remote Protocol
    [MS-DSSP]: Directory Services Setup Remote Protocol Intellectual Property Rights Notice for Open Specifications Documentation . Technical Documentation. Microsoft publishes Open Specifications documentation (“this documentation”) for protocols, file formats, data portability, computer languages, and standards support. Additionally, overview documents cover inter-protocol relationships and interactions. Copyrights. This documentation is covered by Microsoft copyrights. Regardless of any other terms that are contained in the terms of use for the Microsoft website that hosts this documentation, you can make copies of it in order to develop implementations of the technologies that are described in this documentation and can distribute portions of it in your implementations that use these technologies or in your documentation as necessary to properly document the implementation. You can also distribute in your implementation, with or without modification, any schemas, IDLs, or code samples that are included in the documentation. This permission also applies to any documents that are referenced in the Open Specifications documentation. No Trade Secrets. Microsoft does not claim any trade secret rights in this documentation. Patents. Microsoft has patents that might cover your implementations of the technologies described in the Open Specifications documentation. Neither this notice nor Microsoft's delivery of this documentation grants any licenses under those patents or any other Microsoft patents. However, a given Open Specifications document might be covered by the Microsoft Open Specifications Promise or the Microsoft Community Promise. If you would prefer a written license, or if the technologies described in this documentation are not covered by the Open Specifications Promise or Community Promise, as applicable, patent licenses are available by contacting [email protected].
    [Show full text]
  • Pingdirectory Administration Guide Version
    Release 7.3.0.3 Server Administration Guide PingDirectory | Contents | ii Contents PingDirectory™ Product Documentation................................................ 20 Overview of the Server............................................................................. 20 Server Features.................................................................................................................................20 Administration Framework.................................................................................................................21 Server Tools Location....................................................................................................................... 22 Preparing Your Environment....................................................................22 Before You Begin.............................................................................................................................. 22 System requirements..............................................................................................................22 Installing Java......................................................................................................................... 23 Preparing the Operating System (Linux).......................................................................................... 24 Configuring the File Descriptor Limits.................................................................................... 24 File System Tuning.................................................................................................................25
    [Show full text]
  • Oracle Internet Directory 11G R1
    2 3 Directory services are key building blocks for secure identity-enabled business applications and the underlying enterprise identity management (IdM) architecture. Well-structured and organized directory services are the foundation of efficient and effective security services. This is because all IDM applications and most commercial off the shelf (COTS) business applications that require a standard mechanism to access identity attributes, and the most common way to access identity attributes is using LDAP. Example identity attributes include user credentials, access privileges and profile information. Additionally the modern enterprise has different identity attribute needs than they did when LDAP servers first appeared on the market in the 1990s. This is because modern enterprises often have multiple LDAP storage-based servers as well as identity stored in non-LDAP repositories such as HR or CRM databases. Furthermore, new computing initiatives, such as mobile computing, cloud computing and social networking, require LDAP to manage extremely large number of objects, to deliver high performance to manage dynamic data like location and presence, and to be elastic to grow with the cloud. These requirements led to several challenges in deploying identity related applications within the enterprise: While Microsoft Active Directory is pervasive within enterprises, it does not provide the functionality to be a general purpose Enterprise Directory Service because of limitations imposed on it being the Network Operating System directory for Windows. To address Active Directory limitations, Microsoft provides Active Directory Lightweight Directory Services (AD LDS)1. However, due to AD LDS‟s application specific nature, the 1 AD LDS formerly known as Active Directory Application Mode (ADAM) 4 proliferation of AD LDS within enterprises is like weeds in a garden resulting in cost and manageability issues.
    [Show full text]
  • Open Directory Administration for Version 10.5 Leopard Second Edition
    Mac OS X Server Open Directory Administration For Version 10.5 Leopard Second Edition Apple Inc. © 2008 Apple Inc. All rights reserved. The owner or authorized user of a valid copy of Mac OS X Server software may reproduce this publication for the purpose of learning to use such software. No part of this publication may be reproduced or transmitted for commercial purposes, such as selling copies of this publication or for providing paid-for support services. Every effort has been made to make sure that the information in this manual is correct. Apple Inc., is not responsible for printing or clerical errors. Apple 1 Infinite Loop Cupertino CA 95014-2084 www.apple.com The Apple logo is a trademark of Apple Inc., registered in the U.S. and other countries. Use of the “keyboard” Apple logo (Option-Shift-K) for commercial purposes without the prior written consent of Apple may constitute trademark infringement and unfair competition in violation of federal and state laws. Apple, the Apple logo, iCal, iChat, Leopard, Mac, Macintosh, QuickTime, Xgrid, and Xserve are trademarks of Apple Inc., registered in the U.S. and other countries. Finder is a trademark of Apple Inc. Adobe and PostScript are trademarks of Adobe Systems Incorporated. UNIX is a registered trademark of The Open Group. Other company and product names mentioned herein are trademarks of their respective companies. Mention of third-party products is for informational purposes only and constitutes neither an endorsement nor a recommendation. Apple assumes no responsibility with regard to the performance or use of these products.
    [Show full text]
  • Red Hat Enterprise Ipa
    RED HAT ENTERPRISE IPA INTRODUCTION Red Hat Enterprise IPA enables your organization to comply with regulations, reduce risk, and become more efficient. Simply and centrally manage your Linux/Unix users and their authentication today. And in the future, your Linux/Unix machines, services, policy, and audit information. Government and industry compliance regulations, as well as best practice risk reduction principles require an organization to establish: • the administrative users accessing machines and services on those machines • which machines and services users have accessed • the actions those users took • policies to control user access to particular machines and service • policies around password strength to protect against unauthorized access Establishing these things simply and centrally, in addition to the obvious security benefits, brings significant efficiencies such as: • reduced time and manual work in an internal or external audit • reduced time spent adjusting parameters and policies for individual machines • more rapid deployment and migration of workloads in the environment • increased ability to benefit from initiatives such as Red Hat Linux Automation www.dlt.com/redhat Red Hat Enterprise IPA | Karl Wirth EXISTING SOLUTIONS To solve these problems, organizations have essentially three options. Roll your own solution; purchase an expensive proprietary solution; or leverage an existing Microsoft Active Directory infrastructure for your Unix/Linux identity and policy. ROLL YOUR OWN For over a decade, organizations have used Sun’s Network Information Services (NIS) and NIS+ to provide central management of identity and policy for users and machines in the Linux and Unix environment. NIS has some serious weaknesses that could cause NIS to fail some security compliance audits.
    [Show full text]
  • Openls Directory Service Architectures and Implementation Based on Web-Service
    OpenLS Directory Service Architectures and Implementation based on Web-Service Jae-Chul Kim, Sung-Soo Kim, Tae-Wook Heo, Jong-Hyun Park LBS Team, Spatial Information Technology Center, ETRI 161 Kajong-Dong, Yusong-Gu, Daejon, Korea [email protected] Abstract: In this paper, we developed those Directory Services used to describe any kind of content in a structured way, based on the Web-Service, because Web-Service environments separated from its presentation to a specific device [2]. provide a suitable method to gather requested information in an SOAP (Simple Object Access Protocol) is a network, appropriate way. The proposed architecture cooperate with transport, and programming language-neutral protocol other OpenLS(Open Location Service) Core Services ( Location that allows a client to call a remote service. The message Utility Service and Router Determin ation service) and is an format is XML [3]. interoperability one — it identifies those global elements of the global Web-Services network that are required in order to en- WSDL (Web-services description language) is an sure interoperability between Web-Services. In this paper, a XML-based interface and implementation description new architecture of Directory Service with OpenLS Core Ser- language. The service provider uses a WSDL document vices is proposed and tested in OpenLS Core Services envi- in order to specify the operations a Web-Service pro- ronments. vides, as well as the parameters and data types of these Keywords: Web-Service, Directory service, OpenLS. operations. A WSDL document also contains the service access information [4]. UDDI (universal description, discovery, and integra- 1. Introduction tion) is both a client-side API and a SOAP-based server implementation that can be used to store and retrieve information on service providers and Web-Services [5].
    [Show full text]
  • Solaris™ Naming and Directory Service
    SOLARIS™NAMING AND DIRECTORY SERVICE THE SOLARIS™ OPERATING ENVIRONMENT LDAP AS A NAMING SERVICE The Solaris™ 8 Operating Environment is the established OS leader Solaris 8 introduces support for LDAP as the access protocol for for availability, scalability, and security in the Internet age. In Solaris naming services. LDAP is a directory standard defined by the Internet 8 software, Sun delivers a trustworthy, universal platform to meet Engineering Task Force (IETF). The Solaris 8 Operating Environment the needs of .com businesses — from small startups to large lets you define information such as usernames, host names, Fortune 1000 enterprises. passwords, and other network resources on any directory server (for example, the iPlanet™ Directory Server) supporting the LDAP v3 It’s no surprise that the Solaris Operating Environment is the leading protocol. The LDAP server stores this information in a hierarchical UNIX® environment today. Solaris software was originally designed namespace called a Directory Information Tree (DIT). The DIT with the Internet in mind. TCP/IP, the central Internet protocol, has consists of entries that are composed of attribute-value pairs. been at the core of Solaris networking for more than 15 years. Each attribute has a type and can have one or more values. Through its time-tested design — a small, stable kernel, modular Naming information, such as host names and passwords, and extensible components, and well-defined interfaces — Solaris will be stored in these entries as attribute values. software delivers rock-solid stability and predictability for business- critical applications. And the Solaris 8 Operating Environment In the Solaris 8 Operating Environment, LDAP clients can use the provides complete compatibility with prior versions, so you can LDAP v3 protocol to access naming information from LDAP servers.
    [Show full text]
  • Amhs) Description
    INTERNATIONAL CIVIL AVIATION ORGANIZATIONA ASIA AND PACIFIC OFFICE ASIA/PACIFIC REGIONAL AERONAUTICAL TELECOMMUNICATION NETWORK (ATN) AIR TRAFFIC SERVICE (ATS) MESSAGE HANDLING SYSTEM (AMHS) DESCRIPTION First Edition – April 2005 Reference Document for the AMHS Description TABLE OF CONTENTS 1.0 INTRODUCTION............................................................................................................................3 1.1 SCOPE................................................................................................................................... 3 1.2 STANDARD COMPLIANCE ....................................................................................................... 3 1.2.1 ICAO Doc 9705 Edition 2 and Edition 3 ................................................................................. 3 1.3 Introduction to the ATS Message Handling System (AMHS)......................................................... 4 1.3.1 Aeronautical Fixed Telecommunications Network (AFTN) ........................................................... 4 1.3.2 OSI X.400 Message Handling System............................................................................................. 5 1.3.3 ATS Message Handling Service (ATSMHS) .................................................................................. 6 1.3.4 ATS Message Handling System (AMHS) ....................................................................................... 7 1.4 Initial AMHS Configuration...........................................................................................................
    [Show full text]