أنت تعرض محتوى المساعدة للإصدار:
- 6.3
- 6.2
- الإصدارات الأقدم
Configure AEM so that a replication agent on the author instance uses mutual SSL (MSSL) to connect with the publish instance. Using MSSL, the replication agent and the HTTP service on the publish instance use certificates to authenticate each other.
Configuring MSSL for replication involves performing the following steps:
- Create or obtain private keys and certificates for the author and publish instances.
- Install the keys and certificates on the author and publish instances:
- Author: Author's private key and Publish's certificate.
- Pubish: Publish's private key and Author's certificate. The certificate is associated with the user account that is authenticated with the replication agent.
- Configure the Jetty-Based HTTP Service on the Publish instance.
- Configure the transport and SSL properties of the replication agent.

You must determine which user account is performing the replication. When installing the trusted author certificate on the publish instance, the certificate is associated with this user account.
You require a private key and public certificate for the author and publish instances:
- Private keys must be contained in pkcs#12 or JKS format.
- Certificates must be contained in pkcs#12 or JKS format. Additionally certificate contained in "CER" format can also be added to Granite Truststore.
- Certificates can be self-signed or signed by a recognized CA.
Generate a private key and a certificate in JKS format. The private key is stored in a KeyStore file, and the certificate is stored in a TrustStore file. Use Java keytool to create both.
Perform the following steps using Java keytool to create the private key and the credential:
- Generate a private-public key pair in a KeyStore.
- Create or obtain the certificate:
- Self-signed: Export the certificate from the KeyStore.
- CA-signed: Generate a certificate request and send it to the CA.
- Import the certificate into a TrustStore.
-
Open a command-line window or terminal. To create the private-public key pair, enter the following command, using option values from the table below:
keytool -genkeypair -keyalg RSA -validity 3650 -alias alias -keystore keystorename.keystore -keypass key_password -storepass store_password -dname "CN=Host Name, OU=Group Name, O=Company Name,L=City Name, S=State, C=Country_ Code"
-
keytool -exportcert -alias alias -file cert_file -storetype jks -keystore keystore -storepass store_password
Generate a private key and a certificate in pkcs#12 format. Use openSSL to generate them. Use the following procedure to generate a private key and a certificate request. To obtain the certificate, either sign the request with your private key (self-signed certificate) or send the request to a CA. Then, generate the pkcs#12 archive that contains the private key and the certificate.
Install the following items on the author instance:
- The private key of the author instance.
- The certificate of the publish instance.
-
Open the User Management page for the author instance. (http://localhost:4502/libs/granite/security/content/useradmin.html)
-
Open the User Management page for the author instance. (http://localhost:4502/libs/granite/security/content/useradmin.html)
Install the following items on the publish instance:
- The private key of the publish instance.
- The certificate of the author instance. Associate the certificate with the user that is used to execute replication requests.
-
Open the User Management page for the publish instance. (http://localhost:4503/libs/granite/security/content/useradmin.html)
-
Open the User Management page for the publish instance. (http://localhost:4503/libs/granite/security/content/useradmin.html)
Configure the properties of the Apache Felix Jetty Based HTTP Service on the publish instance so that it uses HTTPS while accessing Granite Keystore. The PID of the service is org.apache.felix.http.
The following table lists the OSGi properties that you need to configure whether you are using the Web Console.
Property Name on Web Console | OSGi Property Name | Value |
---|---|---|
Enable HTTPS | org.apache.felix.https.enable | true |
Enable HTTPS To Use Granite KeyStore | org.apache.felix.https.use.granite.keystore | true |
HTTPS Port | org.osgi.service.http.port.secure | 8443 (or other desired port) |
Client Certificate | org.apache.felix.https.clientcertificate | "Client Certificate Wanted" |
Configure the replication agent on the author instance to use the HTTPS protocol when connecting to the publish instance. For complete information about configuring replication agents see Configuring Your Replication Agents.
To enable MSSL, configure the properties on the Transport tab according to the following table:
Property | Value |
---|---|
URI | https://server_name:SSL_port/bin/receive?sling:authRequestLogin=1 For example: https://localhost:8443/bin/receive?sling:authRequestLogin=1 |
User | No value |
Password | No value |
SSL | Client Auth |

After you configure the replication agent, test the connection to determine whether MSSL is configured correctly.
29.08.2014 14:02:46 - Create new HttpClient for Default Agent 29.08.2014 14:02:46 - * HTTP Version: 1.1 29.08.2014 14:02:46 - * Using Client Auth SSL configuration * 29.08.2014 14:02:46 - adding header: Action:Test 29.08.2014 14:02:46 - adding header: Path:/content 29.08.2014 14:02:46 - adding header: Handle:/content 29.08.2014 14:02:46 - deserialize content for delivery 29.08.2014 14:02:46 - No message body: Content ReplicationContent.VOID is empty 29.08.2014 14:02:46 - Sending POST request to https://localhost:8443/bin/receive?sling:authRequestLogin=1 29.08.2014 14:02:46 - sent. Response: 200 OK 29.08.2014 14:02:46 - ------------------------------------------------ 29.08.2014 14:02:46 - Sending message to localhost:8443 29.08.2014 14:02:46 - >> POST /bin/receive HTTP/1.0 29.08.2014 14:02:46 - >> Action: Test 29.08.2014 14:02:46 - >> Path: /content 29.08.2014 14:02:46 - >> Handle: /content 29.08.2014 14:02:46 - >> Referer: about:blank 29.08.2014 14:02:46 - >> Content-Length: 0 29.08.2014 14:02:46 - >> Content-Type: application/octet-stream 29.08.2014 14:02:46 - -- 29.08.2014 14:02:46 - << HTTP/1.1 200 OK 29.08.2014 14:02:46 - << Connection: Keep-Alive 29.08.2014 14:02:46 - << Server: Day-Servlet-Engine/4.1.64 29.08.2014 14:02:46 - << Content-Type: text/plain;charset=utf-8 29.08.2014 14:02:46 - << Content-Length: 26 29.08.2014 14:02:46 - << Date: Fri, 29 Aug 2014 18:02:46 GMT 29.08.2014 14:02:46 - << Set-Cookie: login-token=3529326c-1500-4888-a4a3-93d299726f28%3ac8be86c6-04bb-4d18-80d6-91278e08d720_98797d969258a669%3acrx.default; Path=/; HttpOnly; Secure 29.08.2014 14:02:46 - << Set-Cookie: cq-authoring-mode=CLASSIC; Path=/; Secure 29.08.2014 14:02:46 - << 29.08.2014 14:02:46 - << R 29.08.2014 14:02:46 - << eplicationAction TEST ok. 29.08.2014 14:02:46 - Message sent. 29.08.2014 14:02:46 - ------------------------------------------------ 29.08.2014 14:02:46 - Replication (TEST) of /content successful. Replication test succeeded