As this is my sixth post on Identity Management I thought it would (first) be wise to explain (and link back to) my previous efforts. My first post kicked off the series by outlining challenges associated with interoperability in the modern enterprise. My second post explored how the integration gap between Linux systems and Active Directory emerged, how it was formerly addressed, and what options are available now. My third post outlined the set of criteria with which one is able to examine various integration options. And my most recent entries, post four and five, reviewed options for direct and indirect integration, respectively.
Delving deeper into the world of indirect integration (i.e. utilizing a trust-based approach) – two of the biggest questions are often: “Where are my users?” and “Where does authentication actually happen?” As opposed to a solution that relies upon synchronization (more…)
As product manager for Red Hat Enterprise Linux 7, part of my job is to ensure that the latest version of our flagship product adheres to our promise of stability, reliability, and security. In addition, as Red Hat Enterprise Linux 7 is Red Hat’s latest enterprise Linux platform, it also needs to incorporate new innovations in technology to help our customers gain business advantage, reduce costs, and increase efficiency without compromising their existing investments. With this in mind, the Red Hat Enterprise Linux team takes great care in evaluating new technology to ensure that it is introduced in a manner that is minimally intrusive (if at all) and is a natural fit for the platform. Support for Linux containers and the ability to host container-based applications are great examples of this and Red Hat Enterprise Linux 7 stands ready for the challenge.
Creating and operating application containers via process isolation is not a new concept. Red Hat Enterprise Linux 6 sowed the seeds for this way back in 2010 with the introduction of Control Groups (cgroups). Since that time there have been many exciting developments in this area with active participation from Red Hat. Building upon cgroups functionality, enhancements to the kernel combined with an easy-to-use container format (Docker) make now an opportune time to consider deploying container-based applications on Red Hat Enterprise Linux 7.
Here are the top three reasons to consider Red Hat Enterprise Linux 7 as the host for your container-based applications (more…)
The main alternative to direct integration of Linux/UNIX systems into Active Directory (AD) environments is the indirect approach – where Linux systems are first connected to a central server and this server is then somehow connected to AD. This approach is not new. Over the years many environments have deployed LDAP servers to manage their Linux/UNIX systems (using this LDAP server) while users were stored in AD. To reconcile this issue and to enable users from AD to access Linux systems – users and their passwords were routinely synchronized from AD. While this approach is viable – it’s also quite limited and prone to error. In addition, there is little value in having a separate LDAP server. The only reason for such a setup is to have a separation of duties between Linux and Windows administrators. The net result is that the overhead is quite high while the value of such an approach is quite low.
When IdM (Identity Management in Red Hat Enterprise Linux based on FreeIPA technology) emerged, many environments were either considering direct integration or were “in-process” with respect to adoption. How, exactly, does IdM work? IdM provides (more…)
Linux containers are disrupting traditional application development and deployment models, enabling businesses to explore new, better ways to deliver products and services. How are organizations like yours using containers?
Join Transform Application Delivery with Containers | A Red Hat virtual event on March 12, and learn how containers can add value for your organization.
In this event, you’ll gain insights into (more…)
As mentioned in my previous post there are multiple ways to connect a Linux system to Active Directory (AD) directly. With this in mind, let us review the following list of options…
- The legacy integration option: this is a solution where (likely older) native Linux tools are used to connect to an LDAP server of your choice (e.g. AD).
- The traditional integration option: this is a solution based on Samba winbind.
- The third-party integration option: this is a solution based on (proprietary) commercial software.
- The contemporary integration option: this is a solution based on SSSD.
Legacy Integration Option
In the case of the legacy integration option (see figure above), a Linux system is connected to AD using LDAP for identity lookup and LDAP or Kerberos for authentication. It pretty much solves the problem of basic user authentication. That said, such a solution has the following significant limitations: (more…)
Linux permanently changed the landscape of the datacenter by creating a community approach to rapid innovation. Its introduction and widespread adoption have fueled a shift from closed to open systems, often times providing greater resiliency than other operating environments. Commodity x86 architectures are only one slice of a much larger market for reliable open source enterprise-class systems – and Linux has for many years been a cross-platform operating system. For example, did you know that Red Hat Enterprise Linux also runs on IBM’s Power Systems (POWER) and z Systems architectures? These options give IT organizations flexibility with respect to hardware for workloads and use cases ranging from big data analytics to cloud computing. Ensuring that Red Hat Enterprise Linux runs on IBM’s Power Systems and z Systems architectures gives our customers a broad range of application and deployment choices.
Red Hat Enterprise Linux for Power and Red Hat Enterprise Linux for System z are built (more…)
In my previous post I reviewed the trends related to the integration of Linux systems into environments managed by Active Directory (AD). In this post I will review two integration options, namely: direct integration and indirect integration.
The direct option is, not surprisingly, when your systems are integrated into AD directly (i.e. your Linux systems communicate directly with AD), while the indirect option leverages an intermediary server (see figure below). (more…)
Red Hat and Cisco have a long history of offering joint solutions that benefit our mutual customers and address a gamut of IT challenges, from server sprawl to cloud computing. Both companies consistently foster technological innovation and work towards breaking new ground in computing, including a history of driving world-record performance across a wide range of industry-standard benchmarks.
Industry standard performance benchmarking, driven by groups like TPC and SPEC, goes all the way back to 1988. Many of these benchmarks have driven the development of faster, cheaper, and more efficient computer technologies over the course of the past quarter century.
With over a hundred of benchmark records to its name, Red Hat Enterprise Linux is known to power some of the most (more…)
This post is the second in a series of blog posts about integrating Linux systems into Active Directory environments. In the previous post we discussed dishwashers and, more seriously, some basic principles. In this post I will continue by exploring how the integration gap between Linux systems and Active Directory emerged, how it was formerly addressed, and what options are available now.
Let’s start with a bit of history… before the advent of Active Directory, Linux and UNIX systems had developed ways to connect to, and interact with, a central LDAP server for identity look-up and authentication purposes. These connections were basic, but as the environments were not overly complex (in comparison to modern equivalents) – they were good enough for the time. Then… AD was born.
Active Directory not only integrated several services (namely: LDAP, Kerberos, and DNS) under one hood, but it also (more…)
Have you ever purchased a new dishwasher? For those of you who have, you know that the dishes don’t get washed until your “purchase” is picked-up/delivered, the old dishwasher is removed, and the new unit is hooked-up. In fact, until the new dishwasher is hooked-up, it simply doesn’t work. The dishwasher can be smart, stylish, noiseless, and/or energy-efficient… but none of this matters if it’s not properly connected. At the end of the day, if you want to enjoy the luxury of automatic dish washing, one thing is clear: your new dishwasher needs to be hooked-up.
The act of hooking-up a dishwasher is not unlike adding a Linux system to an existing enterprise IT environment. When you deploy a Linux system, it too needs to be “hooked-up”. As the data that flows through your environment consists of different kinds of objects (e.g. users, groups, hosts, and services) the associated identity information is not unlike the water in your dishwasher. Without this identity information (more…)