DOCSLIB.ORG

Integration with Active Directory Jeremy Allison Samba Team

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Integration with Active Directory Jeremy Allison Samba Team Integration with Active Directory Jeremy Allison Samba Team Benefits of using Active Directory •Unlike the earlier Microsoft Windows NT 4.x Domain directory service which used proprietary DCE/RPC calls, Active Directory is based on standard Internet protocols. •LDAPv3 for directory lookup and updates. •Kerberos 5 for authentication (single sign on). •DNS for name resolution. •The hope was that non-Microsoft implementations of these protocols could be used to serve Windows clients allowing true competition for providing these services. •Unfortunately this is not the case. What is Active Directory ? Dynamic DNS Server DHCP Server Kerberos 5 Server (KDC) Database Back end Store LDAPv3 Server Microsoft RPC Domain server Why must we use an Active Directory Server ? •Windows clients don©t use only the standard protocols to achieve logon services. •Mandatory ªextraº features (like the modified Kerberos ticket and other details) are tied into the Active Directory implementation to enforce vendor lock-in. •The practical result of this is that if you want to use Windows clients and servers and obtain all the functionality you paid for then you must use a Windows Active Directory server. •IT Staff who recommend an Active Directory roll out without making management aware of this commitment going forward are misleading their executive staff. Why must we use an Active Directory Server ? •Windows clients do not allow replacement of their low-level functionality to ease integration with non-Windows directory servers. •As usual, it is easier to configure non-Windows systems to interoperate with Windows systems than vica-versa. •The free release of Microsoft Services for UNIX does help here, although the protocols used (NIS) are not as secure as using the native protocols of Kerberos and LDAP. •Active Directory servers can have their LDAP schema (the formal definition of the format of the data they store) extended to allow them to serve non-Windows clients. What do we mean by integration with an Active Directory Server ? •For a non-Windows client to integrate successfully into Active Directory we need two operations to be seamless. •Authentication of Linux/UNIX accounts against Active Directory. •Enumeration of Linux/UNIX user and group directory information stored in an Active Directory store. •For authentication the preferred method is Kerberos 5 (the native Windows 2000 and above authentication method). •Microsoft Services for UNIX, LDAP or MS-RPC can also be used here. •For user and group enumeration integration LDAP is the preferred method. •Microsoft Services for UNIX and MS-RPC can also be used. •Active Directory Servers can be Kerberos 5 KDC servers for Linux/UNIX clients. •MIT or Heimdal Kerberos servers cannot be complete KDC servers for Windows clients due to the missing ªextraº data field. Kerberos Authentication •MIT or Heimdal KDC servers can be set to ªtrustº AD Kerberos Integration servers if the Windows and UNIX user accounts are separated into separate ªrealmsº. •In a more integrated environment it is probably easier to just use Active Directory Kerberos Servers (as Microsoft intended by ªextendingº the standard). Integrating Windows Authentication Services with Linux/UNIX •Linux/UNIX systems started with local files containing all authentication information. •Since then a standardized plug-in architecture has been developed to allow replacement of the authentication information validation (user logons) and maintenance (password changing) with many different possible targets. •PAM (Pluggable Authentication Modules) ± API invented by Sun and adopted by Linux and other UNIX platforms. PAM ± Pluggable Authentication Modules Application PAM requests can be for auth, account, PA r M password or session functionality. eq ue st Application PAM library lookup PAM M odu Config S le tack Directory PAM library PAM library PAM library PAM on Linux/UNIX systems •PAM is a standard on Linux and many UNIX systems (HPUX, Solaris and others). •Over twenty different PAM modules exist to provide all manner of authentication services. •Three specific modules are of interest for Active Directory Integration •Kerberos ± pam_krb5 (http://pam-krb5.sourceforge.net) •LDAP ± pam_ldap (http://www.padl.com) •Samba/Microsoft RPC ± pam_winbind ( http://www.samba.org) Kerberos - pam_krb5 •Takes the users clear-text password and validates it against a standard Kerberos 5 server (Active Directory adds extra proprietary data into the returned ticket, but the client libraries on Linux/UNIX ignore this data). •Returns a Kerberos 5 Ticket-Granting-Ticket (TGT) which can be used to get tickets for other services. •Care must be taken to ensure the encryption method used by default by Windows (RC4-HMAC) is available on the Linux/UNIX Kerberos system. •Source code available, Open Source/Free Software. LDAP - pam_ldap •Takes the users clear-text password and validates it against an LDAP server by attempting to set up an LDAP connection as the given username/password pair. •Must be set up to use SSL/TLS in order to securely validate the password (pam_krb5 doesn©t have this problem, all kerberos exchanges are secure). •Developed by PADL software ± available as Open Source/Free Software. Samba - pam_winbind •Allows a Linux/UNIX user to authenticate in exactly the same way as if they were logging on to a Microsoft member server in the Domain. •Requires a working Samba set-up (more details later). •Completely integrates the Linux/UNIX authentication mechanism into the Windows world ± identical to a Windows server. •All of Samba is Open Source/Free Software. Integrating Windows User Directory Services with Linux/UNIX •Linux/UNIX systems started with only local directory listings (local files) and have since had to develop standardized plug-in architectures to allow replacement of the directory service with any compatible server (no hidden protocols). •NSS (Name Service Switch). •NSS allows user and group lookup and enumeration to be done via many different directory services. The order in which they are queried can be changed. •The nss modules that are of interest for Active Directory Integration are : – nss_ldap – nss_winbind – nss_nis NSS ± Name Service Switch Application NSS requests can look up user, group, or N SS enumerate the user or group lists. re qu es t /etc/nsswitch.conf Application NSS library (libc) lookup Mo dule Stac k External lookup NSS library (NIS) Local files NSS library lookup l lookup NSS library Externa (winbind) LDAP - nss_ldap •Written by PADL software (as is pam_ldap) this library allows Linux/UNIX systems to look up users and groups stored in an Active Directory server. •The Active Directory Schema must have been extended from the standard schema by including either the RFC2307 schema (created by PADL) or the schema used by Microsoft©s Services for UNIX product. •The Linux/UNIX user and group information must already exist in the Active Directory as part of the schema. •This requires some extra administration to add the extra information to the existing Active Directory data. Samba - nss_winbind •Part of the complete solution provided by Samba (will be described in detail later). •Does not require any changes to the Active Directory Schema. •Does require a working Samba set up and the Linux/UNIX machine to have been added as a ªmember serverº into the Active Directory. Microsoft Services for UNIX - nss_nis •Does not talk directly to the Active Directory Server but to a NIS (Network Information Services) gateway running on a Windows server. •As with nss_ldap, requires additions to be made to the Active Directory Schema to add the Linux/UNIX (POSIX) definitions. •Useful for older UNIX installations that will only use the NIS protocols (regarded as insecure in modern UNIX systems). •NIS protocol developed by Sun in late 1980©s. Three Complete Solutions for Active Directory Integration PADL solution •Modify Active Directory with either the RFC2307 schema definition or the Microsoft Services for UNIX schema. •Install pam_ldap (or alternatively pam_krb5) to handle the authentication from the Linux/UNIX systems. •Install nss_ldap to handle the directory service enumeration from the Linux/UNIX systems. •Probably the easiest choice for organizations with significant existing Linux/UNIX experience. •Secure, robust solution but requires work to maintain. Services for UNIX solution NIS Server Service Communication using NIS Windows Active protocol over the network. Directory Server (modified schema) Linux/UNIX Server NIS PAM NIS NSS Services for UNIX solution •Uses older NIS protocol ± an older UNIX standard. •Modern Linux/UNIX systems use either NISPLUS (encrypted version of NIS) or LDAP or Kerberos for password verification. •Now Microsoft has made Services for UNIX available for free this is now a competitive solution. •No source code available, unlike other solutions. •Good choice if an organization is mainly Windows, with a few older Linux/UNIX machines for which security is not a priority. Samba winbind solution Windows Active winbind Directory Server daemon (unmodified schema) Linux/UNIX Server winbind PAM MS-RPC or LDAP communication over the network. winbind NSS Samba winbind solution •Allows a Linux/UNIX machine to completely emulate a Windows member server. •No changes to Active Directory schema needed ± winbind copes with mapping Windows users and groups to Linux/UNIX users and groups. •Allows Windows clients accessing file and print (Samba) services on the Linux/UNIX server to pass kerberos 5 tickets to obtain service (as to a Windows file server). •To synchronize user and group mapping between multiple Linux/UNIX servers using winbind an external LDAP server must be used (not completely transparent). •Uses the same protocols as Windows servers for enumerating users and groups and checking passwords. Integrating Samba Windows Active Directory Server t hip M us ns em Tr io Se b lat rv er Re er Samba Domain Windows Controller Application Server r e M b e r m e S b m e e e v rv r r er M e S Conclusions •Windows Active Directory is a necessary evil if you have large numbers of Windows clients.
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]
  • 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 ....................
    [Show full text]