관리형 자동화를 위한 사용자 지정 애플리케이션 설정

CertCentral 관리형 자동화는 가장 널리 사용되는 웹 서버 애플리케이션을 즉시 지원합니다.

CertCentral은 또한 "사용자 지정 애플리케이션" 옵션을 통해 타사 ACME 클라이언트 구성을 허용하여 기본적으로 지원되지 않는 추가 애플리케이션에 대한 인증서 관리를 확장하도록 유연성을 제공합니다.

사용자 지정 애플리케이션에 대해 관리형 자동화를 사용하려면 다음 단계를 따르세요.

Step 1: Install DigiCert agent

Custom automations require an active DigiCert agent on the server. The agent coordinates automation requests received from the Trust Lifecycle Manager web console and calls your custom shell script to handle certificate lifecycle events for the custom application.

For detailed instructions about how to install and activate DigiCert agents on your servers, see Deploy and manage agents.

타사 ACME 클라이언트 설정

In addition to a DigiCert agent, the server must have Certbot installed. Your custom automation script invokes the Certbot ACME client to request certificates from Trust Lifecycle Manager and install them for your custom Linux or Windows application.

For detailed instructions about how to download and install the Certbot client, refer to the official Certbot instructions.

Step 3: Create shell script

You need a shell script to drive certificate lifecycle events for your custom application. When a new certificate is needed, the DigiCert agent calls this shell script to invoke the Certbot client, which then requests the certificate through the Trust Lifecycle Manager ACME service.

The shell script contains the Certbot command to request and install certificates for your custom application using the parameters expected by the Trust Lifecycle Manager ACME service.

Below are examples of shell scripts to enable Trust Lifecycle Manager managed automation for custom Linux and Windows applications.

예 1. Linux

directoryuri=$1
host=$2
emailaddress=$3
eabkeyidentifier=$5
eabkeyhmac=$6
process_path=/usr/bin/apachectl
server_root=/etc/httpd
config_root=/etc/httpd/config
procCmdLine="/usr/bin/apachectl start"
acmeConfigDirectory="/etc/letsencrypt/"
certbot --server $directoryuri --config-dir $acmeConfigDirectory --eab-kid $eabkeyidentifier  --eab-hmac-key $eabkeyhmac --installer apache -m $emailaddress --force-renew --agree-tos --no-redirect --expand -d $host --no-verify-ssl --no-autorenew --pre-hook "$process_path stop" --post-hook $procCmdLine -n --apache-server-root $server_root --apache-vhost-root $config_root
returnCode=$?
echo "The command exit status : ${returnCode}"
exit $returnCode

예 2. Windows

directoryuri=%1
host=%2
emailaddress=%3
eabkeyidentifier=%5
eabkeyhmac=%6
acmeConfigDirectory="./%eabkeyidentifier%"
certbot --server %directoryuri% --config-dir %acmeConfigDirectory% --eab-kid %eabkeyidentifier%  --eab-hmac-key %eabkeyhmac% -m %emailaddress% --force-renew --agree-tos --no-redirect --expand -d %host% --no-verify-ssl --no-autorenew 
set returnCode=%errorlevel%
EXIT /B %returnCode%

Variable definitions at the top of these shell scripts set the required ACME request parameters:

These must match up with the ACME arguments you configure for the custom application in Trust Lifecycle Manager.
During an automation event, values for these arguments are supplied to the shell script by the local DigiCert agent that calls it.

Commands used in the shell script:

Must include all mandatory parameters.
Must not exceed 512 characters.
Must not include special directives like rm -rf or rmdir

The shell script filename:

Must end with .sh or .bat.
Must not exceed 255 characters.

관리형 자동화 설정 구성

CertCentral 자동화 관리 메뉴를 사용하여 사용자 지정 애플리케이션에 대한 구성을 완료합니다.

CertCentral 계정의 왼쪽 메인 메뉴에서 자동화 > 자동화 관리로 이동합니다.
From the More actions dropdown at top, select Add script.
Fill out the Add script form:
1. Name: Enter a user-friendly name to use when referencing the script.
2. Operating system: Select the applicable operating system (Linux or Windows).
3. Script type: Select Custom automation.
4. Script filename: Enter the script's filename in or path relative to the local agent's user-scripts sub-directory.
  - Linux: If your script is named "myscript.sh" and is stored directly in the agent's user-scripts sub-directory, enter myscript.sh here. If you stored the script within an additional sub-directory called "custom-apps" in the user-scripts sub-directory, enter custom-apps/myscript.sh instead.
  - Windows: If your script is named "myscript.bat" and is stored directly in the agent's user-scripts folder, enter myscript.bat here. If you stored the script within an additional sub-folder called "custom-apps" in the user-scripts folder, enter custom-apps\myscript.bat instead.
  주의
  Make sure there are no spaces in the filename for either Linux or Windows. The script will fail if the path or filename has spaces in it.
5. Command-line arguments: Enter a space-separated list of general ACME parameters to use with your custom automation script.
  예:
  {acmeDirectoryUrl} {hosts} {email} {key} {extActKid} {extActHmac}
  유의 사항:
  - 각 인수는 여기에 표시된 대로 정확하게 입력해야 합니다.
  - 인수의 순서는 셸 스크립트에서 사용되는 방식과 일치해야 합니다.
  - 자동화 이벤트 중에 이러한 인수에 필요한 값은 선택한 자동화 프로필에서 자동으로 가져옵니다.
  CertCentral 관리형 자동화에서 지원하는 ACME 인수에 대한 설명:
  - {acmeDirectoryUrl} – ACME 디렉터리 URL 설정.
  - {hosts} – 인증서 호스트 세부 정보.
  - {email} – 알림용 이메일 주소.
  - {key} – 키 알고리즘(RSA 또는 ECC).
  - {extActKid} – URL에 사용되는 외부 계정 키 식별자.
  - {extActHmac} – 응답 서명을 위한 HMAC 키.
6. Description (optional): Enter an optional description for the script to help identify it when working with DigiCert agents and agent-based automations in Trust Lifecycle Manager.
자동화 관리 보기에서 사용자 지정 애플리케이션과 동일한 인증서 호스트에서 실행 중인 로컬 ACME 에이전트의 이름을 선택합니다.

Step 5: Assign script to the applicable agent IP/port targets

To complete the custom automation configuration, assign the script to any DigiCert agents that will coordinate certificate lifecycle automation events for the custom application:

From the Trust Lifecycle Manager main menu, select Discovery & automation tools > Agents.
Locate the local DigiCert agents on the systems where the custom application is running. Select each agent by name to view the details for it.
Select the pencil (edit) icon on the right of the agent details page to update the agent configuration.
In the IP/port targets section for the agent, locate any IP/port targets where the custom application is running and configure them as follows:
- Application: Select Custom.
- Custom automation script: Select the custom automation script by the name assigned to it in Trust Lifecycle Manager.
Select the Update button at bottom to save your changes.

What's next

After enabling managed automation for your custom application, you can schedule certificate lifecycle automation events for it as you would any other server application in Trust Lifecycle Manager.

이 섹션의 내용: