Oracle Solaris 9部署指南：iPlanet目录服务器5.1版详解

需积分: 5 163 浏览量更新于2024-06-22 收藏 1.04MB PDF 举报

身份认证购VIP最低享 7 折!

领优惠券(最高得80元）

Oracle Solaris 9 - Deployment Guide for iPlanet Directory Server-198 是一份针对Oracle Solaris 9操作系统的部署手册，特别针对iPlanet Directory Server第五版（Version 5.1）。该文档发布于2002年2月，版权归属Sun Microsystems, Inc. 和 Netscape Communications Corporation，后者在软件中也贡献了部分内容。书中详细介绍了如何在Solaris 9环境中部署和管理iPlanet Directory Server，这是一款用于存储、管理和查询目录信息的核心服务系统。 iPlanet Directory Server是基于Netscape Directory Server技术，提供了一套企业级的身份和访问管理解决方案。它支持统一身份管理，帮助企业实现对网络资源的集中控制和访问权限的管理。这份指南涵盖了安装、配置、安全设置以及性能优化等关键步骤，旨在确保用户能够顺利地将iPlanet Directory Server整合到Solaris 9平台中，提升组织的信息安全性与管理效率。作为Oracle的一部分，Solaris 9提供了强大的UNIX操作系统基础，而iPlanet Directory Server则扩展了其在目录服务方面的功能。手册中还提及了使用的一些专有技术和商标，如Sun、SunTone、iPlanet等，这些都是Sun Microsystems在国际上的注册商标。此外，文档中还提到了与第三方技术的合作，比如与PEER Networks, Inc. 的版权关系，以及Taligent的Unicode Collation Classes，以及与Regent of the University of Michigan的部分软件源代码授权。本指南不仅适用于IT管理员和系统工程师，对于任何希望在Oracle Solaris 9环境中实施和维护目录服务的组织来说，都是一个重要的参考资源。阅读并遵循此文档中的指导，将有助于确保目录服务的稳定运行，以及在处理大量用户数据时的高效性能和数据一致性。在部署过程中，可能涉及的知识点包括但不限于：操作系统集成、目录设计原则、安全策略、备份与恢复、以及监控和故障排除技巧。

资源详情

资源推荐

Introduction to iPlanet Directory Server

16 iPlanet Directory Server Deployment Guide • February 2002

You can use Directory Server to manage extranet user-authentication, create access

control, set up user preferences, and centralize user management. In hosted

environments, partners, customers, and suppliers can manage their own portions

of the directory, reducing administrative costs.

When you install Directory Server, the following components are installed on your

machine:

• An LDAP server (Directory Server) with a plug-in interface

The name of this process is ns-slapd.

• iPlanet Administration Server

For more information about the Administration Server, go to

http://iplanet.com/products/iplanet_application/.

• iPlanet Console to manage the servers

For more information about the iPlanet Console, see the Console

documentation at http://docs.iplanet.com/docs/manuals/console.html.

• Command-line tools for starting and stopping the server, importing and

exporting data in the database, database reindexing, account inactivation and

deactivation, LDIF merges, and kernel tuning

For more information about the command-line tools, refer to the iPlanet

Directory Server Configuration, Command, and File Reference.

• An SNMP monitor

For more information about SNMP monitoring, refer to the iPlanet Directory

Server Administrator’s Guide.

This guide talks about the core Directory Server and the plug-ins it uses for doing

its work. The next sections describe Directory Server in more detail. The topics

discussed are:

• “Overview of Directory Server Architecture,” on page 16

• “Directory Server Data Storage,” on page 19

Overview of Directory Server Architecture

At installation, Directory Server contains the following:

• A server front-end responsible for network communications

• Plug-ins for server functions, such as access control and replication

Introduction to iPlanet Directory Server

Chapter 1 Introduction to Directory Server 17

• A basic directory tree containing server-related data.

The following sections describe each component of the directory in more detail.

Overview of the Server Front-End

The server front-end of Directory Server manages communications with directory

client programs. Directory Server functions as a daemon. Multiple client programs

can speak to the server in LDAP. They can communicate using LDAP over TCP/IP.

The connection can also be protected with SSL/TLS, depending on whether the

client negotiates the use of Transport Layer Security (TLS) for the connection.

When communication takes place with TLS, the communication is usually

encrypted. In the future, when DNS security is present, TLS used in conjunction

with secured DNS will provide confirmation to client applications that they are

binding to the correct server. If clients have been issued certificates, TLS can be

used by iPlanet Directory Server to confirm that the client has the right to access

the server. TLS and its predecessor SSL are used throughout iPlanet Directory

Server products to perform other security activities such as message integrity

checks, digital signatures, and mutual authentication between servers.

Multiple clients can bind to the server at the same time over the same network

because the Directory Server is a multi-threaded application. As directory services

grow to include larger numbers of entries or larger numbers of clients spread out

geographically, they also include multiple Directory Servers placed in strategic

places around the network.

Server Plug-ins Overview

Directory Server relies on plug-ins. A plug-in is a way to add functionality to the

core server. For example, a database is a plug-in.

A plug-in can be disabled. When disabled, the plug-in’s configuration information

remains in the directory but its function is not used by the server. Depending upon

what you want your directory to do, you can choose to enable any of the plug-ins

provided with Directory Server.

iPlanet Professional Services can write custom plug-ins for your Directory Server

deployment. Contact iPlanet Professional Services for more information.

Overview of the Basic Directory Tree

The directory tree, also known as a directory information tree or DIT, mirrors the

tree model used by most file systems, with the tree’s root, or first entry, appearing

at the top of the hierarchy. At installation, Directory Server creates a default

directory tree.

Introduction to iPlanet Directory Server

20 iPlanet Directory Server Deployment Guide • February 2002

About Directory Entries

LDIF (LDAP Data Interchange Format) is a standard text-based format for

describing directory entries. An entry is a group of lines in the LDIF file that

contains information about an object, such as a person in your organization or a

printer on your network. Information about the entry is represented in the LDIF

file by a set of attributes and their values. Each entry has an object class attribute

that specifies the kind of object the entry describes and defines the set of additional

attributes it contains. Each attribute describes a particular trait of an entry.

For example, an entry might have the object class organizationalPerson,

indicating that the entry represents a person within a particular organization. This

object class allows the givenname and telephoneNumber attributes. The values

assigned to these attributes give the name and phone number of the person

represented by the entry.

iPlanet Directory Server also uses read-only attributes that are calculated by the

server. These attributes are called operational attributes. There are also some

operational attributes that can be set by the administrator, for access control and

other server functions.

Entries are stored in a hierarchical structure in the directory tree. In LDAP, you can

query an entry and request all entries below it in the directory tree. This subtree is

called the base distinguished name, or base DN. For example, if you make an

LDAP search request specifying a base DN of ou=people, dc=siroe,dc=com,

then the search operation examines only the ou=people subtree in the

dc=siroe,dc=com directory tree.

However, all entries are not automatically returned in response to an LDAP search.

Entries of the ldapsubentry object class are not returned in response to normal

search requests. An ldapsubentry entry represents an administrative object, for

example the entries that are used internally by Directory Server to define a role or a

class of service. To receive these entries, clients need to search specifically for

entries of the ldapsubentry object class.

For more information about roles, see “Managed, Filtered, and Nested Roles,” on

page 71. For more information about class of service, see “Class of Service,” on

page 73.

Distributing Directory Data

When you store various parts of your tree in separate databases, your directory can

process client requests in parallel, improving performance. You can also store your

databases on different machines, to further improve performance.

剩余197页未读，继续阅读

weixin_40191861_zj

粉丝: 67
资源: 1万+

会员权益专享

Oracle Solaris 9部署指南：iPlanet目录服务器5.1版详解

Solaris9下安装Oracle9操作指南.doc

Error from server (NotFound): deployments.apps "tomcat-deployment" not found

我想把k8s-node1上面正在运行的一个名为nginx-deployment的pod扩容出来一个放到node2节点上运行，实现让node1节点上的nginx-deployment和node2节点上的同时存在

camunda.bpm.auto-deployment-enabled

The Deployment "alluxio-deployment" is invalid: spec.template.metadata.labels: Invalid value: map[string]string{"app":"alluxio"}: `selector` does not match template `labels`

kube-hyperf-deployment.yaml文件中如何添加spec: securityContext: runAsUser: 0 containers: - name: my-container image: my-image字段

kcl apply -f webshare-pvc.yaml kcl apply -f deployment.yaml kcl apply -f deployment-svc.yaml kcl apply -f deployment-ingress.yaml

[root@node1 ~/storage]#kubectl apply -f nfs-deployment.yaml deployment.apps/nfs-provisioner unchanged

是否可以先通过kubectl get 备份资源为yaml,然后再修改yaml文件，最后通过kubectl apply更新配置文件。还有通过sh脚本方式，怎么更新资源配置。

apiVersion: v1 kind: Service metadata: name: springboot-svc namespace: kubesphere-sample-devvqmj9 spec: selector: app: springboot-test-deployment ports: - protocol: TCP port: 7654 # Service port targetPort: 7654 type: NodePort 如何我使用 该服务器的ip加上port是否可以访问到

deployment怎么扩容或缩容

kube-hyperf-deployment.yaml创建pod报错Failed to pull image "hyperf": rpc error: code = Unknown desc = Error response from daemon: pull access denied for hyperf, repository does not exist or may require 'docker login': denied: requested access to the resource is denied怎么解决如何排查

用MATLAB生成一个500500200的三维水下监测区域，共进行200个节点的部署。生成一个运行结果，然后再将这200个节点进行随机部署在三维水下监测区域，使用self-deployment算法将节点进行分簇，生成运行结果

error: unable to recognize "zabbix-server-deployment.yaml": no matches for kind "Deployment" in version "v1"

写一个yaml文件部署一个demo Deployment

k8s deployment 清单

域控制器结构设计参考资料

使用kubernetv1.18 创建一个Deployment三副本的nginx并映射文件夹 创建pod完成后通过映射路径上传html

SoftKeyboard软件版本1.0.0压

会员权益专享

最新资源

apiVersion: v1 kind: Service metadata: name: springboot-svc namespace: kubesphere-sample-devvqmj9 spec: selector: app: springboot-test-deployment ports: - protocol: TCP port: 7654 # Service port targetPort: 7654 type: NodePort 如何我使用该服务器的ip加上port是否可以访问到

使用kubernetv1.18 创建一个Deployment三副本的nginx并映射文件夹创建pod完成后通过映射路径上传html