Skip to content

Commit 3f3e4d8

Browse files
committed
Document obtaining CA bundle in a separate module
1 parent a314c70 commit 3f3e4d8

File tree

3 files changed

+31
-4
lines changed

3 files changed

+31
-4
lines changed

guides/common/assembly_using-the-mcp-server-for-project.adoc

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -4,4 +4,6 @@ include::modules/con_using-the-mcp-server-for-project.adoc[]
44

55
include::modules/con_overview-of-project-mcp-integration.adoc[leveloffset=+1]
66

7+
include::modules/proc_obtaining-the-location-of-the-ca-bundle-for-project.adoc[leveloffset=+1]
8+
79
include::assembly_generating-reports-by-using-the-mcp-server-for-project.adoc[leveloffset=+1]

guides/common/modules/proc_configuring-the-mcp-server-for-project.adoc

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -12,10 +12,8 @@ Perform these steps on the same system where your MCP client will run.
1212
ifdef::satellite[]
1313
* You are logged in to the registry.redhat.io container registry.
1414
endif::[]
15-
* The CA bundle for your {Project} is available on your system.
16-
If you are using the default self-signed {Project} certificate, the CA bundle is located at `_{foreman-example-com}_/pub/katello-server-ca.crt`.
17-
+
18-
If the MCP client runs on a system other than the {ProjectServer}, your {Project} administrator can download the CA bundle from the {ProjectServer} and transfer it to your system.
15+
* The certificate authority (CA) bundle for your {Project} is available on your system and you know its location.
16+
For more information, see xref:obtaining-the-location-of-the-ca-bundle-for-{project-context}[].
1917

2018
.Procedure
2119
. Optional: Pull the latest version of the MCP container image from the registry:
Lines changed: 27 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,27 @@
1+
[id="obtaining-the-location-of-the-ca-bundle-for-{project-context}"]
2+
= Obtaining the location of the CA bundle for {Project}
3+
4+
[role="_abstract"]
5+
To deploy the MCP server for {Project}, the CA bundle for {Project} must be available on the system where the MCP server is being deployed.
6+
The CA bundle is the certificate of a CA which signed the certificate that is used to secure {ProjectWebUI}.
7+
8+
Perform these steps on your {ProjectServer} or ask your administrator to perform them for you.
9+
10+
.Procedure
11+
. Locate the CA bundle.
12+
For example, if you are using the default self-signed {Project} certificate, obtain the CA bundle location by inspecting the *SSLCACertificateFile* value in the `/etc/httpd/conf.d/05-foreman-ssl.conf` file:
13+
+
14+
[options="nowrap", subs="+quotes,attributes"]
15+
----
16+
# cat /etc/httpd/conf.d/05-foreman-ssl.conf | awk -F '"' '/SSLCACertificateFile/ { print $2 }'
17+
----
18+
+
19+
The default location is
20+
ifdef::katello,orcharhino,satellite[]
21+
`/etc/pki/katello/certs/katello-default-ca.crt`
22+
endif::[]
23+
ifdef::foreman-deb,foreman-el[]
24+
`/etc/puppetlabs/puppet/ssl/certs/ca.pem`
25+
endif::[]
26+
.
27+
. If you are deploying the MCP server on a system other than your {ProjectServer}, transfer the CA bundle to that system.

0 commit comments

Comments
 (0)