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-zos&topic=tagt_wlp_collective_security
파일 이름: tagt_wlp_collective_security.html