,欢迎您!
登录您的红帽帐户
尚未注册?下面是您应该进行注册的一些理由:
- 从一个位置浏览知识库文章、管理支持案例和订阅、下载更新以及执行其他操作。
- 查看组织内的用户,以及编辑他们的帐户信息、偏好设置和权限。
- 管理您的红帽认证,查看考试历史记录,以及下载认证相关徽标和文档。
您可以使用红帽帐户访问您的会员个人资料、偏好设置以及其他服务,具体决取决于您的客户状态。
出于安全考虑,如果您在公共计算机上通过红帽服务进行培训或测试,完成后务必退出登录。
退出红帽博客
Blog menu
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).
Before we dive into an overview and detailed comparison of these two integration options we need to define “the aspects of the integration”. The aspects of integration are:
- Authentication - A user logs into a Linux system, how is he or she authenticated?
- Identity Lookup - How does a given system know about the right accounts? How are Active Directory accounts are mapped to accounts used on Linux?
- Name Resolution and Service Discovery - How does a system know where to find its authentication and identity server?
- Policy Management - How are other identity related policies are managed on the system?
Having outlined this set of criteria, my next post will use it towards reviewing both the direct and indirect integration options in greater detail.