DOCSLIB.ORG

Improving Client Side in the Age of Samba AD and Freeipa

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Improving Client Side in the Age of Samba AD and Freeipa Enterprise desktop: improving client side in the age of Samba AD and FreeIPA Principal Software Engineer, Red Hat // Samba Team Alexander Bokovoy SambaXP’16 Enterprise desktop? Enterprise desktop: improving client side in the age of Samba AD and FreeIPA 2 Centralized identity management system There are now several free software identity management systems with the focus on managing operating systems’ environments: I Samba AD I FreeIPA I [many other LDAP+Kerberos based projects] Enterprise desktop: improving client side in the age of Samba AD and FreeIPA 3 Enterprise desktop I a client enrolled to a centralized identity management system I a tool to solve business tasks I a subject to centrally defined access controls Enterprise desktop: improving client side in the age of Samba AD and FreeIPA 4 I authentication services: logon details, mostly via PAM interface I authorization services: mostly via PAM interface or application-specific ones Enterprise desktop Typical enterprise desktop includes agents for I identity services: POSIX attributes for users and groups via NSSWITCH Enterprise desktop: improving client side in the age of Samba AD and FreeIPA 5 I authorization services: mostly via PAM interface or application-specific ones Enterprise desktop Typical enterprise desktop includes agents for I identity services: POSIX attributes for users and groups via NSSWITCH I authentication services: logon details, mostly via PAM interface Enterprise desktop: improving client side in the age of Samba AD and FreeIPA 6 Enterprise desktop Typical enterprise desktop includes agents for I identity services: POSIX attributes for users and groups via NSSWITCH I authentication services: logon details, mostly via PAM interface I authorization services: mostly via PAM interface or application-specific ones Enterprise desktop: improving client side in the age of Samba AD and FreeIPA 7 I pam_sss use is configured at the enrollment time for system-auth PAM service which is included to all PAM configurations I SSSD performs host-based access control to PAM services using rules stored centrally in FreeIPA I OpenSSH is configured to look up public keys for users and hosts via SSSD I SUDO is configured to look up SUDO rules in FreeIPA via SSSD I automount can be configured to use SSSD to deliver the mount maps I SSSD provides locator and localauth plugins to MIT Kerberos to discover domain controllers and map Kerberos principals to POSIX user names for trust operations I SSSD supports offline logon, logon with smart cards, logon with Kerberos proxy Practical case: Fedora and FreeIPA FreeIPA client defaults to use SSSD as an agent I nss_sss is referenced in /etc/nsswitch.conf on Fedora by default Enterprise desktop: improving client side in the age of Samba AD and FreeIPA 8 I SSSD performs host-based access control to PAM services using rules stored centrally in FreeIPA I OpenSSH is configured to look up public keys for users and hosts via SSSD I SUDO is configured to look up SUDO rules in FreeIPA via SSSD I automount can be configured to use SSSD to deliver the mount maps I SSSD provides locator and localauth plugins to MIT Kerberos to discover domain controllers and map Kerberos principals to POSIX user names for trust operations I SSSD supports offline logon, logon with smart cards, logon with Kerberos proxy Practical case: Fedora and FreeIPA FreeIPA client defaults to use SSSD as an agent I nss_sss is referenced in /etc/nsswitch.conf on Fedora by default I pam_sss use is configured at the enrollment time for system-auth PAM service which is included to all PAM configurations Enterprise desktop: improving client side in the age of Samba AD and FreeIPA 9 I OpenSSH is configured to look up public keys for users and hosts via SSSD I SUDO is configured to look up SUDO rules in FreeIPA via SSSD I automount can be configured to use SSSD to deliver the mount maps I SSSD provides locator and localauth plugins to MIT Kerberos to discover domain controllers and map Kerberos principals to POSIX user names for trust operations I SSSD supports offline logon, logon with smart cards, logon with Kerberos proxy Practical case: Fedora and FreeIPA FreeIPA client defaults to use SSSD as an agent I nss_sss is referenced in /etc/nsswitch.conf on Fedora by default I pam_sss use is configured at the enrollment time for system-auth PAM service which is included to all PAM configurations I SSSD performs host-based access control to PAM services using rules stored centrally in FreeIPA Enterprise desktop: improving client side in the age of Samba AD and FreeIPA 10 I SUDO is configured to look up SUDO rules in FreeIPA via SSSD I automount can be configured to use SSSD to deliver the mount maps I SSSD provides locator and localauth plugins to MIT Kerberos to discover domain controllers and map Kerberos principals to POSIX user names for trust operations I SSSD supports offline logon, logon with smart cards, logon with Kerberos proxy Practical case: Fedora and FreeIPA FreeIPA client defaults to use SSSD as an agent I nss_sss is referenced in /etc/nsswitch.conf on Fedora by default I pam_sss use is configured at the enrollment time for system-auth PAM service which is included to all PAM configurations I SSSD performs host-based access control to PAM services using rules stored centrally in FreeIPA I OpenSSH is configured to look up public keys for users and hosts via SSSD Enterprise desktop: improving client side in the age of Samba AD and FreeIPA 11 I automount can be configured to use SSSD to deliver the mount maps I SSSD provides locator and localauth plugins to MIT Kerberos to discover domain controllers and map Kerberos principals to POSIX user names for trust operations I SSSD supports offline logon, logon with smart cards, logon with Kerberos proxy Practical case: Fedora and FreeIPA FreeIPA client defaults to use SSSD as an agent I nss_sss is referenced in /etc/nsswitch.conf on Fedora by default I pam_sss use is configured at the enrollment time for system-auth PAM service which is included to all PAM configurations I SSSD performs host-based access control to PAM services using rules stored centrally in FreeIPA I OpenSSH is configured to look up public keys for users and hosts via SSSD I SUDO is configured to look up SUDO rules in FreeIPA via SSSD Enterprise desktop: improving client side in the age of Samba AD and FreeIPA 12 I SSSD provides locator and localauth plugins to MIT Kerberos to discover domain controllers and map Kerberos principals to POSIX user names for trust operations I SSSD supports offline logon, logon with smart cards, logon with Kerberos proxy Practical case: Fedora and FreeIPA FreeIPA client defaults to use SSSD as an agent I nss_sss is referenced in /etc/nsswitch.conf on Fedora by default I pam_sss use is configured at the enrollment time for system-auth PAM service which is included to all PAM configurations I SSSD performs host-based access control to PAM services using rules stored centrally in FreeIPA I OpenSSH is configured to look up public keys for users and hosts via SSSD I SUDO is configured to look up SUDO rules in FreeIPA via SSSD I automount can be configured to use SSSD to deliver the mount maps Enterprise desktop: improving client side in the age of Samba AD and FreeIPA 13 I SSSD supports offline logon, logon with smart cards, logon with Kerberos proxy Practical case: Fedora and FreeIPA FreeIPA client defaults to use SSSD as an agent I nss_sss is referenced in /etc/nsswitch.conf on Fedora by default I pam_sss use is configured at the enrollment time for system-auth PAM service which is included to all PAM configurations I SSSD performs host-based access control to PAM services using rules stored centrally in FreeIPA I OpenSSH is configured to look up public keys for users and hosts via SSSD I SUDO is configured to look up SUDO rules in FreeIPA via SSSD I automount can be configured to use SSSD to deliver the mount maps I SSSD provides locator and localauth plugins to MIT Kerberos to discover domain controllers and map Kerberos principals to POSIX user names for trust operations Enterprise desktop: improving client side in the age of Samba AD and FreeIPA 14 Practical case: Fedora and FreeIPA FreeIPA client defaults to use SSSD as an agent I nss_sss is referenced in /etc/nsswitch.conf on Fedora by default I pam_sss use is configured at the enrollment time for system-auth PAM service which is included to all PAM configurations I SSSD performs host-based access control to PAM services using rules stored centrally in FreeIPA I OpenSSH is configured to look up public keys for users and hosts via SSSD I SUDO is configured to look up SUDO rules in FreeIPA via SSSD I automount can be configured to use SSSD to deliver the mount maps I SSSD provides locator and localauth plugins to MIT Kerberos to discover domain controllers and map Kerberos principals to POSIX user names for trust operations I SSSD supports offline logon, logon with smart cards, logon with Kerberos proxy Enterprise desktop: improving client side in the age of Samba AD and FreeIPA 15 I Pure winbindd: nss_winbind and pam_winbind for identity and authentication I Pure winbindd: Limited authorization capabilities (account lock) I Hybrid approach: I nss_sss and pam_sss for identity and authentication I winbindd is used by Samba, configured to trust SSSD-provided ID range I SSSD supports offline logon, logon with smart cards, logon with Kerberos proxy I SSSD does authorization using GPO and/or account lock Practical case: Samba AD domain member I A pure winbindd-based setup or a hybrid SSSD+winbindd configuration Enterprise desktop:
Load more

Recommended publications
  • Automating Identity Management with Ansible Automation
    Automating Identity Management with Ansible Automation Brad Krumme Solutions Architect 1 INTRODUCTION SysAdmin Background RHCE and Ansible Specialist Love Sports/Performance Cars Also love Craft Beer and Bourbon Brad Krumme Solutions Architect 2 Agenda What we’ll ▸ Overview of Red Hat Identity Management ▸ Overview of Ansible Automation Platform discuss today ▸ Identity Management Automation Use Case ▸ Ansible Setup Considerations ▸ Automation In Practice ▸ Extra Resources 3 Red Hat Identity Red Hat Identity Management provides a centralized and clear Management Overview method for managing identities for users, machines, and services within large Linux/Unix enterprise environments. 4 IdM Server - responsibilities Identity Store ● Users, Hosts, Services ● Groups (User and Host) Authentication ● Passwords, 2FA (Smart Cards, OTP soft/hard tokens) ● SSO ● What is expected from the Client/Server certificates (PKI) service? Authorization ● Access rules per host ● Privileged operations ● IdM itself - RBAC - user roles and admin delegations Security-related service management ● Secrets (passwords) ● Linux - SUDO, SELinux, etc. 5 Auditing and reporting IdM Server - standard Infrastructure ● LDAP: old & proven protocol for sharing data, interfaces sometimes authentication too (v3 from *1997) ● Kerberos: old & proven protocol for authentication (*1993, revised 2005) ● Deprecated: NIS, NTLM How Identity Servers interact Applications with the outer world ● LDAP: user details, often authentication too ● Kerberos: authentication (SSO), mostly for internal
    [Show full text]
  • Release Notes for Fedora 20
    Fedora 20 Release Notes Release Notes for Fedora 20 Edited by The Fedora Docs Team Copyright © 2013 Fedora Project Contributors. The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at http://creativecommons.org/licenses/by-sa/3.0/. The original authors of this document, and Red Hat, designate the Fedora Project as the "Attribution Party" for purposes of CC-BY-SA. In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version. Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law. Red Hat, Red Hat Enterprise Linux, the Shadowman logo, JBoss, MetaMatrix, Fedora, the Infinity Logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries. For guidelines on the permitted uses of the Fedora trademarks, refer to https:// fedoraproject.org/wiki/Legal:Trademark_guidelines. Linux® is the registered trademark of Linus Torvalds in the United States and other countries. Java® is a registered trademark of Oracle and/or its affiliates. XFS® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries. MySQL® is a registered trademark of MySQL AB in the United States, the European Union and other countries. All other trademarks are the property of their respective owners.
    [Show full text]
  • Freeipa 1.2.1 Installation and Deployment Guide
    freeIPA 1.2.1 Installation and Deployment Guide IPA Solutions from the IPA Experts Installation and Deployment Guide freeIPA 1.2.1 Installation and Deployment Guide IPA Solutions from the IPA Experts Edition 1.0 Copyright © 2008 Red Hat. This material may only be distributed subject to the terms and conditions set forth in the Open Publication License, V1.0 or later. The latest version of the OPL is presently available at http://www.opencontent.org/openpub/. Red Hat and the Red Hat "Shadow Man" logo are registered trademarks of Red Hat, Inc. in the United States and other countries. All other trademarks referenced herein are the property of their respective owners. The GPG fingerprint of the [email protected] key is: CA 20 86 86 2B D6 9D FC 65 F6 EC C4 21 91 80 CD DB 42 A6 0E 1801 Varsity Drive Raleigh, NC 27606-2072 USA Phone: +1 919 754 3700 Phone: 888 733 4281 Fax: +1 919 754 3701 PO Box 13588 Research Triangle Park, NC 27709 USA This guide covers the basic considerations that should be addressed before deploying IPA. It also covers the installation and configuration of each of the supported server platforms. Preface v 1. Audience ........................................................................................................................ v 2. Document Conventions ................................................................................................... v 2.1. Typographic Conventions ...................................................................................... v 2.2. Pull-quote Conventions .......................................................................................
    [Show full text]
  • Integrating Openshift Enterprise with Identity Management (Idm) in Red Hat Enterprise Linux
    Integrating OpenShift Enterprise with Identity Management (IdM) in Red Hat Enterprise Linux OpenShift Enterprise 2.2 IdM in Red Hat Enterprise Linux 7 Windows Server 2012 - Active Directory Integration Mark Heslin Principal Systems Engineer Version 1.1 January 2015 1801 Varsity Drive™ Raleigh NC 27606-2072 USA Phone: +1 919 754 3700 Phone: 888 733 4281 Fax: +1 919 754 3701 PO Box 13588 Research Triangle Park NC 27709 USA Linux is a registered trademark of Linus Torvalds. Red Hat, Red Hat Enterprise Linux and the Red Hat "Shadowman" logo are registered trademarks of Red Hat, Inc. in the United States and other countries. Microsoft and Windows are U.S. registered trademarks of Microsoft Corporation. UNIX is a registered trademark of The Open Group. Intel, the Intel logo and Xeon are registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. All other trademarks referenced herein are the property of their respective owners. © 2014 by Red Hat, Inc. This material may be distributed only subject to the terms and conditions set forth in the Open Publication License, V1.0 or later (the latest version is presently available at http://www.opencontent.org/openpub/). The information contained herein is subject to change without notice. Red Hat, Inc. shall not be liable for technical or editorial errors or omissions contained herein. Distribution of modified versions of this document is prohibited without the explicit permission of Red Hat Inc. Distribution of this work or derivative of this work in any standard (paper) book form for commercial purposes is prohibited unless prior permission is obtained from Red Hat Inc.
    [Show full text]
  • Deploying Red Hat Openshift Container Platform 3.6 on Microsoft Azure
    Reference Architectures 2017 Deploying Red Hat OpenShift Container Platform 3.6 on Microsoft Azure Last Updated: 2018-01-12 Reference Architectures 2017 Deploying Red Hat OpenShift Container Platform 3.6 on Microsoft Azure Glenn West Ryan Cook Eduardo Minguez [email protected] Legal Notice Copyright © 2018 Red Hat, Inc. The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at http://creativecommons.org/licenses/by-sa/3.0/ . In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version. Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law. Red Hat, Red Hat Enterprise Linux, the Shadowman logo, JBoss, OpenShift, Fedora, the Infinity logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries. Linux ® is the registered trademark of Linus Torvalds in the United States and other countries. Java ® is a registered trademark of Oracle and/or its affiliates. XFS ® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries. MySQL ® is a registered trademark of MySQL AB in the United States, the European Union and other countries. Node.js ® is an official trademark of Joyent. Red Hat Software Collections is not formally related to or endorsed by the official Joyent Node.js open source or commercial project.
    [Show full text]
  • Enterprise Desktop at Home with Freeipa and GNOME
    Enterprise desktop at home with FreeIPA and GNOME Alexander Bokovoy ([email protected]) January 30th, 2016 FOSDEM’16 Enterprise? Enterprise desktop at home with FreeIPA and GNOME 2 * almost local office network is not managed by a company’s IT department Enterprise desktop at home with FreeIPA and GNOME 3 * almost company services’ hosting is cloudy there is no one cloud to rule them all Enterprise desktop at home with FreeIPA and GNOME 4 I Home-bound identity to access local resources I Cloud-based (social networking) identities I Free Software hats to wear I Certificates and smart cards to present myself legally I Private data to protect and share * almost I have FEW identities: I A corporate identity for services sign-on I want them to be usable at the same time Enterprise desktop at home with FreeIPA and GNOME 5 I Cloud-based (social networking) identities I Free Software hats to wear I Certificates and smart cards to present myself legally I Private data to protect and share * almost I have FEW identities: I A corporate identity for services sign-on I Home-bound identity to access local resources I want them to be usable at the same time Enterprise desktop at home with FreeIPA and GNOME 6 I Free Software hats to wear I Certificates and smart cards to present myself legally I Private data to protect and share * almost I have FEW identities: I A corporate identity for services sign-on I Home-bound identity to access local resources I Cloud-based (social networking) identities I want them to be usable at the same time Enterprise desktop
    [Show full text]
  • Freeipa Global Catalog Challenges
    FreeIPA Global Catalog challenges Samba XP - 2020 May 27 Alexander Bokovoy Florence Blanc-Renaud Red Hat / Samba team Red Hat Alexander: ● Samba team member since 2003 ● FreeIPA core developer since 2011 Florence ● LDAP server technology engineer since 2007 ● FreeIPA core developer since 2016 Samba: ● Andreas Schneider ● Isaac Boukris ● Simo Sorce 389-ds LDAP server ● Thierry Bordaz ● William Brown Thank you all! ● Mark Reynolds ● Ludwig Krispenz MIT Kerberos ● Greg Hudson ● Robbie Harwood ● Isaac Boukris ● Simo Sorce and many others Allow access to Active Directory resources for IPA users and services Frankenstein's Active Directory: for Linux clients, not Windows Uses 389-ds LDAP server, MIT Kerberos, and Samba NT domain controller code base to implement what Active Directory domain controller sees as a separate Active Directory forest ▸ LDAP schema optimized for Linux clients and POSIX identity management use cases ▸ Flat directory information tree for users, groups, and services ▸ No compatibility with Active Directory schema ▸ LDAP objects specific to POSIX environment use cases (SUDO rules, own access control rules, etc) ▸ KDC based on MIT Kerberos, native two-factor authentication and modern pre-authentication methods ▸ NetLogon and LSA pipes with enough support to allow AD DCs to interoperate via a forest trust ▸ Integrated DNS server and Certificate Authority It is not that simple... Global Catalog Entries LDAP is a communication protocol designed with flexibility and extensibility in mind ▸ Schema: ▸ Syntaxes ▸ Attribute types
    [Show full text]
  • Fedora 26 Installation Guide
    Fedora 26 Installation Guide Installing Fedora 26 on 32 and 64-bit AMD and Intel Fedora Documentation Project Installation Guide Fedora 26 Installation Guide Installing Fedora 26 on 32 and 64-bit AMD and Intel Edition 1 Author Fedora Documentation Project Copyright © 2017 Red Hat, Inc. and others. The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at http://creativecommons.org/licenses/by-sa/3.0/. The original authors of this document, and Red Hat, designate the Fedora Project as the "Attribution Party" for purposes of CC-BY-SA. In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version. Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law. Red Hat, Red Hat Enterprise Linux, the Shadowman logo, JBoss, MetaMatrix, Fedora, the Infinity Logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries. For guidelines on the permitted uses of the Fedora trademarks, refer to https://fedoraproject.org/wiki/ Legal:Trademark_guidelines. Linux® is the registered trademark of Linus Torvalds in the United States and other countries. Java® is a registered trademark of Oracle and/or its affiliates. XFS® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries.
    [Show full text]
  • A Guide for Administrators
    User Guide for JBoss Negotiation A Guide for Administrators Darran A. Lofthouse ISBN: Publication date: User Guide for JBoss Negotiation User Guide for JBoss Negotiation: A Guide for Administrators by Darran A. Lofthouse User Guide for JBoss Negotiation Target Audience ............................................................................................... vii Preface ............................................................................................................. ix 1. Introduction to JBoss Negotiation ................................................................... 1 1. Components .......................................................................................... 1 2. General Authentication Process .............................................................. 1 3. Pre-requisits .......................................................................................... 2 2. General Installation ........................................................................................ 3 1. Introduction ........................................................................................... 3 2. Installation ............................................................................................. 3 2.1. Authenticator Installation ............................................................. 3 2.1.1. JBoss AS 4.2.x ................................................................ 3 2.1.2. JBoss AS 5.0.x ................................................................ 4 2.2. Realm Properties .......................................................................
    [Show full text]
  • LINUX JOURNAL | Issue 284 | March 2018
    What’s New Shell Scripting Raspberry Pi in Qubes 4 Security Alternatives Since 1994: The original magazine of the Linux community DEEP DIVE BLOCKCHAIN PLUS POSTGRESQL 10 The Latest and Most Interesting Features BITCOIN AND TAXES Cryptocurrency and Uncle Sam LINUXBOOT FOSS Project Spotlight ISSUE 284 | MARCH 2018 www.linuxjournal.com MARCH 2018 CONTENTS ISSUE 284 DEEP DIVE: Blockchain 95 Blockchain, Part I: Introduction and Cryptocurrency by Petros Koutoupis What makes both bitcoin and blockchain so exciting? What do they provide? Why is everyone talking about this? And, what does the future hold? 105 Blockchain, Part II: Configuring a Blockchain Network and Leveraging the Technology by Petros Koutoupis How to set up a private etherium blockchain using open-source tools and a look at some markets and industries where blockchain technologies can add value. 2 | March 2018 | http://www.linuxjournal.com CONTENTS 6 From the Editor—Doc Searls Help Us Cure Online Publishing of Its Addiction to Personal Data UPFRONT 18 FOSS Project Spotlight: LinuxBoot by David Hendricks, Ron Minnich, Chris Koch and Andrea Barberio 24 Readers’ Choice Awards 26 Shorter Commands by Kyle Rankin 29 For Open-Source Software, the Developers Are All of Us by Derek Zimmer 32 Taking Python to the Next Level by Joey Bernard 37 Learning IT Fundamentals by Kyle Rankin 40 Introducing Zero-K, a Real-Time Strategy Game for Linux by Oflameo 45 News Briefs COLUMNS 46 Kyle Rankin’s Hack and / What’s New in Qubes 4 52 Reuven M. Lerner’s At the Forge PostgreSQL 10: a Great New Version for a Great Database 64 Shawn Powers’ The Open-Source Classroom Cryptocurrency and the IRS 72 Zack Brown’s diff -u What’s New in Kernel Development 76 Susan Sons’ Under the Sink Security: 17 Things 86 Dave Taylor’s Work the Shell Shell Scripting and Security 178 Glyn Moody’s Open Sauce Looking Back: What Was Happening Ten Years Ago? LINUX JOURNAL (ISSN 1075-3583) is published monthly by Linux Journal, LLC.
    [Show full text]
  • Identity Management in Red Hat Enterprise Linux 8 Beta
    Identity Management in Red Hat Enterprise Linux 8 beta Dmitri Pal Director, Software Engineering, Red Hat, Inc. 09-May-2019 What is this presentation about? Let us set expectations! What is this presentation about? ● Who in the audience does not use Identity Management from Red Hat but considers it and came to learn more? What is this presentation about? ● Who in the audience does not use Identity Management from Red Hat but considers it and came to learn more? ● Who in the audience uses Identity Management in Red Hat Enterprise Linux (IdM) and wants to: ○ Learn how to get most out of the solution? ○ Find a solution to a specific problem? ○ Share their experiences about the deployments and discuss challenges and successes? What is this presentation about? ● Building identity management solution for your enterprise ● Getting the most out of your deployment ● What is next ● Staying connected Building an Identity Management solution for your enterprise What do we hear? ● How do I build my overall IdM solution for the enterprise connecting all the layers to avoid fragmentation? ● Should I use the Directory Server or IdM? What is the difference? ● What is the role of the RH-SSO? Is it the same as IdM? ● I have an existing LDAP solution and I need to consolidate around Active Directory (AD), what should I do? IdM vs. Directory Server What is IdM? ● IdM – Identity Management in Red Hat Enterprise Linux ● Based on FreeIPA open source technology ● IPA stands for Identity, Policy, Audit ○ Focused on identities and related policies ○ A separate project is ongoing in the audit space ● Built into operating system - comes with the RHEL subscription What Problems IdM Solves? ● Central management of authentication and identities for Linux clients ○ Improvement over standalone LDAP/Kerberos/NIS based solutions ○ Simplify and automate management of the infrastructure ● Gateway between the Red Hat Enterprise Linux and Active Directory.
    [Show full text]
  • Nicola Canepa's Curriculum Vitae
    Nicola Canepa's Curriculum vitae https://www.nicolacanepa.net/oldsite/Curriculum_Vitae_di_Nico... EUROPEAN CURRICULUM VITAE FORMAT 17 Feb 2018 PERSONAL INFORMATION Name Nicola Canepa Address 1 Burlington Plaza Dublin Ireland Telephone +353-83-8314100 E-mail [email protected] Nationality Italian Date of birth 29/03/1974 WORK EXPERIENCE Dates (from-to) 03/2016-today Name and address of the Amazon Web Services, One Burlington Plaza (Dublin, Ireland) employer Type of business or sector Cloud Occupation or position held Permanent full time contract Main activities and System Developer Engineer in the L7 load balancing team which responsibilities provides load balancing solutions for Amazon internal teams and for customer services. Acquired experience with managing and automating network infrastructure tasks at scale. Started OOP Python programming (API calls, throttling, AAA). Introduction to Java programming (Collections, workflows, threads). Evolution of the Data warehouse analytics platform for the load balancing team. Experience with AWS services (Athena, S3, IAM, CloudWatch, Lambda). Basics of Rubyi. Automation of new region builds (automating tasks in a restricted environment) Dates (from-to) 09/2008-03/2016 Name and address of the MaxMara Fashion Group, Via Giulia maramotti, 4 (Reggio nell'Emilia) employer Type of business or sector Textile Occupation or position held Permanent full time contract Main activities and Senior system and security administrator on Linux/Unix environment, responsibilities implementations for network infrastructure (both hardware and software) and for security infrastructure. TCP/IP network upkeeping. Linux, Mac OSX and Windows server management and installation. Growth experience about: BIND 9, Apache 2.2 and 2.4, IPTables, CISCO PIX, Squid 3, OpenVPN; acquired experience with SAP administration, RedHat (CMAN, corosync, GFS2 clustered FS) cluster, KVM (Linux Kernel-based Virtualization Machine) and Xen, Cisco switches and routers, Cisco VPN, pfSense, Python programming.
    [Show full text]