Liberty 集合のセキュリティーの構成
集合コントローラーおよび集合メンバーのセキュリティーを構成できます。
始める前に
Liberty での集合セキュリティーの原則について、集合のセキュリティーをお読みください。
サブトピック
Setting up collectives with third-party certificates
SSL protects communication between controllers and members. Each server in a collective has its own identity that is composed of its host name, user directory, and server name. Each server in a collective has two keystores that are named by default serverIdentity.jks and collectiveTrust.jks. The keystore contains the SSL certificates that are needed to declare its own identity and securely establish a communication with other members and controllers within the collective. For an application to establish an HTTPS inbound connection, each server has two more keystores that are named by default, key.jks and trust.jks.- Configuring SAF certificates and keyrings for TLS on the z/OS operating system
Migrate an existing collective to use System Authorization Facility (SAF) for security-related functions, such as requests for authentication, authorization, or certificates.
タスク・トピック
最終更新: Tuesday, 6 December 2016http://www14.software.ibm.com/webapp/wsbroker/redirect?version=cord&product=was-nd-dist&topic=tagt_wlp_collective_security
ファイル名: tagt_wlp_collective_security.html