Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ENDOC-535-ssl-note #546

Merged
merged 3 commits into from
Aug 4, 2022
Merged

ENDOC-535-ssl-note #546

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
796abf3
ENDOC-535-ssl-note
jyunmitch Aug 3, 2022
7e15298
ENDOC-535-ssl-note review edit
jyunmitch Aug 3, 2022
c9a76a1
ENDOC-535-ssl-note tiny edit
jyunmitch Aug 3, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions vuepress/docs/next/tutorials/getting-started/openshift-install-by-operator.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -117,6 +117,7 @@ type: kubernetes.io/tls
Now create the `entando-ca-cert-secret` Secret, similar to what was done in Scenario 3, but this time using the self-signed certificate.

4. Go to `Workloads` → `Secrets` → `Create` and select `Key/value secret`
For multiple certificates, see note below on [Certificate Chains](#note-certificate-chains).
5. Set the `Secret Name`, e.g. `entando-ca-cert-secret`
6. Set the `Key`, e.g. `tls.crt`
7. Set the `Value` by clicking `Browse...` and loading the cert file from Step 1, e.g. `tls.crt`
Expand All @@ -140,6 +141,14 @@ Now let's create a new application similar to Scenario 3, but with the self-sign

Once the deployment is complete, you can confirm that all routes use HTTPS with the self-signed certificate. You may still see security warnings in the browser.

#### Note: Certificate Chains
If you have multiple certificates to load into OpenShift, you must pass each with its own identifier.
```bash
ca0.crt: → a single CA certificate
ca1.crt: → another CA certificate
...
ca5.crt → last CA certificate
```
See the [Next Steps](#next-steps) below to continue your work with Entando.

## Next Steps
Expand Down
11 changes: 11 additions & 0 deletions vuepress/docs/v7.0/tutorials/getting-started/openshift-install-by-operator.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -117,6 +117,8 @@ type: kubernetes.io/tls
Now create the `entando-ca-cert-secret` Secret, similar to what was done in Scenario 3, but this time using the self-signed certificate.

4. Go to `Workloads` → `Secrets` → `Create` and select `Key/value secret`
For multiple certificates, see note below on [Certificate Chains](#note-certificate-chains).

5. Set the `Secret Name`, e.g. `entando-ca-cert-secret`
6. Set the `Key`, e.g. `tls.crt`
7. Set the `Value` by clicking `Browse...` and loading the cert file from Step 1, e.g. `tls.crt`
Expand All @@ -140,6 +142,15 @@ Now let's create a new application similar to Scenario 3, but with the self-sign

Once the deployment is complete, you can confirm that all routes use HTTPS with the self-signed certificate. You may still see security warnings in the browser.

#### Note: Certificate Chains
If you have multiple certificates to load into OpenShift, you must pass each with its own identifier.
```bash
ca0.crt: → a single CA certificate
ca1.crt: → another CA certificate
...
ca5.crt → last CA certificate
```

See the [Next Steps](#next-steps) below to continue your work with Entando.

## Next Steps
Expand Down