Skip to content

Commit fda7c90

Browse files
committed
Merge branch 'rmarano/hide-14120-info' into 'main'
Remove refs to 141200 See merge request weblogic-cloud/weblogic-kubernetes-operator!4697 (cherry picked from commit 88f525c) bd51e48 Remove refs to 141200
1 parent e06b7ef commit fda7c90

File tree

3 files changed

+2
-41
lines changed

3 files changed

+2
-41
lines changed

documentation/site/content/managing-domains/major-weblogic-version-upgrade/upgrade-14210.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,6 +2,7 @@
22
title = "Upgrade managed domains to v14.1.2.0"
33
date = 2023-10-05T16:43:45-05:00
44
weight = 7
5+
draft = true
56
pre = "<b> </b>"
67
description = "Upgrade managed domains to v14.1.2.0."
78
+++
@@ -443,7 +444,7 @@ serverPod:
443444

444445
### Sample WDT model for secured production mode and SSL
445446

446-
If you are upgrading an existing domain to 14.1.2.0 and your existing domain does not have secured production mode enabled, the operator, by default, will _disable_ secured production mode. If you want to override this behavior, you must enable it explicitly. Optionally, you can delete the existing domain and let the operator completely rebuild the domain and, by default, secured production mode will be enabled; you do not have to enable it explicitly.
447+
If you are upgrading an existing domain to 14.1.2.0 and your existing domain does not have secured production mode enabled, the operator, by default, will _disable_ secured production mode. If you want to override this behavior, you must enable it explicitly. Optionally, you can delete the existing domain and let the operator completely rebuild the domain and, by default, secured production mode will be enabled; you do not have to enable it explicitly.
447448

448449
The following is a code snippet of a WDT model for setting up secured production mode and SSL.
449450

documentation/site/content/managing-domains/model-in-image/overview.md

Lines changed: 0 additions & 38 deletions
Original file line numberDiff line numberDiff line change
@@ -52,44 +52,6 @@ When you deploy a Model in Image domain resource YAML file:
5252
- The operator subsequently boots your domain's WebLogic Server pods.
5353
- The pods will obtain their domain home from the ConfigMap.
5454

55-
### Using demo SSL certificates in v14.1.2.0.0 or later
56-
57-
{{% notice note %}}
58-
Beginning with WebLogic Server version 14.1.2.0.0, when a domain is `production` mode enabled, it is automatically `secure mode` enabled, therefore, all communications with the domain are using SSL channels and non-secure listening ports are disabled. If there are no custom certificates configured for the SSL channels, then the server uses the demo SSL certificates.
59-
The demo SSL certificates are now domain specific and generated when the domain is first created,
60-
unlike previous releases, which were distributed with the WebLogic product installation. Oracle recommends using custom SSL
61-
certificates in a production environment.
62-
{{% /notice %}}
63-
64-
The certificates are created under the domain home `security` folder.
65-
66-
```
67-
-rw-r----- 1 oracle oracle 1275 Feb 15 15:55 democakey.der
68-
-rw-r----- 1 oracle oracle 1070 Feb 15 15:55 democacert.der
69-
-rw-r----- 1 oracle oracle 1478 Feb 15 15:55 DemoTrust.p12
70-
-rw-r----- 1 oracle oracle 1267 Feb 15 15:55 demokey.der
71-
-rw-r----- 1 oracle oracle 1099 Feb 15 15:55 democert.der
72-
-rw-r----- 1 oracle oracle 1144 Feb 15 15:55 DemoCerts.props
73-
-rw-r----- 1 oracle oracle 2948 Feb 15 15:55 DemoIdentity.p12
74-
```
75-
76-
For Model in Image domains, whenever you change any security credentials including, but not limited to, the Administration Server credentials, RCU credentials, and such, the domain will be recreated and a new set of demo SSL certificates will be generated. The SSL certificates are valid for 6 months, then they expire.
77-
78-
The demo CA certificate expires in 5 years, however, whenever the domain is recreated, the entire set of certificates are regenerated so you _must_ import the demo CA certificate again.
79-
80-
If you have any external client that needs to communicate with WebLogic Servers using SSL, then you need to import the current self-signing CA certificate, `democacert.der`,
81-
into your local trust store.
82-
83-
```shell
84-
keytool -importcert -keystore <keystore path> -alias wlscacert -file $HOME/Downloads/democacer.der
85-
```
86-
87-
If you are using the WebLogic Scripting Tool, before starting the WLST session, you can set the following system properties.
88-
89-
```shell
90-
export WLST_PROPERTIES="-Dweblogic.security.TrustKeyStore=DemoTrust -Dweblogic.security.SSL.ignoreHostnameVerification=true"
91-
```
92-
9355
### Runtime updates
9456

9557
Model updates can be applied at runtime by changing an image, secrets, a domain resource, or a WDT model ConfigMap after initial deployment.

documentation/site/content/managing-domains/model-in-image/runtime-updates.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -42,8 +42,6 @@ the change requires entirely shutting domain the domain,
4242
applying the change, and finally restarting the domain. Full domain restarts are described in
4343
[Full domain restarts]({{< relref "/managing-domains/domain-lifecycle/startup/_index.md#full-domain-restarts">}}).
4444

45-
**NOTE**: If you are using WebLogic Server 14.1.2.0.0 or later, see [Using demo SSL certificates in v14.1.2.0.0 or later]({{< relref "/managing-domains/model-in-image/overview#using-demo-ssl-certificates-in-v141200-or-later" >}}).
46-
4745
**NOTE**: Supported and unsupported changes are described in these sections: [Supported updates](#supported-updates) and [Unsupported updates](#unsupported-updates).
4846
_It is the administrator's responsibility to make the necessary changes to a domain resource to initiate the correct approach for an update._
4947

0 commit comments

Comments
 (0)