Merge branch 'edburns/o-572-remove-key-vault-mentions' into 'main'

On branch edburns/o-572-remove-key-vault-mentions

See merge request weblogic-cloud/weblogic-kubernetes-operator!4999

(cherry picked from commit 4280ff6)

b8f8e22 On branch edburns/o-572-remove-key-vault-mentions

Co-authored-by: Ryan Eberhard <[email protected]>

Author: rjeberhard

documentation/site/content/managing-domains/aks/_index.md

@@ -127,9 +127,9 @@ When you are satisfied with your selections, select **Next** and open **TLS/SSL*
 
 With the **TLS/SSL** blade, you can configure Oracle WebLogic Server Administration Console on a secure HTTPS port, with your own SSL certificate provided by a Certifying Authority (CA). See [Oracle WebLogic Server Keystores configuration](https://aka.ms/arm-oraclelinux-wls-ssl-configuration) for more information.
 
-Select **Yes** or **No** for the option **Configure WebLogic Server Administration Console, Remote Console, and cluster to use HTTPS (Secure) ports, with your own TLS/SSL certificate.** If you select **No**, you don't have to provide any details, and can proceed by selecting **Next**. If you select **Yes**, you can choose to provide the required configuration details by either uploading existing keystores or by using keystores stored in Azure Key Vault.
+Select **Yes** or **No** for the option **Configure WebLogic Server Administration Console, Remote Console, and cluster to use HTTPS (Secure) ports, with your own TLS/SSL certificate.** If you select **No**, you don't have to provide any details, and can proceed by selecting **Next**. If you select **Yes**, you must upload your existing keystores.
 
-If you want to upload existing keystores, select **Upload existing KeyStores** for the option **How would you like to provide required configuration**, and enter the values for the fields listed in the following table.
+Enter the values for the fields listed in the following table.
 
 #### Upload existing KeyStores
 
@@ -147,23 +147,6 @@ If you want to upload existing keystores, select **Upload existing KeyStores** f
 | Confirm password | Re-enter the value of the preceding field. |
 | The Trust KeyStore type (JKS,PKCS12) | Select the type of custom trust keystore. The supported values are JKS and PKCS12. |
 
-If you want to use keystores that are stored in Azure Key Vault, select **Use KeyStores stored in Azure Key Vault** for the option **How would you like to provide required configuration**, and enter the values for the fields listed in the following table.
-
-#### Use KeyStores stored in Azure Key Vault
-
-| Field | Description |
-|-------|-------------|
-| Resource group name in current subscription containing the Key Vault | Enter the name of the Resource Group containing the Key Vault that stores the SSL certificate and the data required for WebLogic SSL termination. |
-| Name of the Azure Key Vault containing secrets for the TLS/SSL certificate | Enter the name of the Azure Key Vault that stores the SSL certificate and the data required for WebLogic SSL termination. |
-| The name of the secret in the specified Key Vault whose value is the Identity KeyStore Data | Enter the name of the Azure Key Vault secret that holds the value of the identity keystore data. Follow [Store the TLS/SSL certificate in the Key Vault](#store-the-tlsssl-certificate-in-the-key-vault) to upload the certificate to Azure Key Vault. |
-| The name of the secret in the specified Key Vault whose value is the passphrase for the Identity KeyStore |  Enter the name of the Azure Key Vault secret that holds the value of the passphrase for the identity keystore. |
-| The Identity KeyStore type (JKS,PKCS12) | Select the type of custom identity keystore. The supported values are JKS and PKCS12. |
-| The name of the secret in the specified Key Vault whose value is the Private Key Alias | Enter the name of the Azure Key Vault secret that holds the value of the private key alias. |
-| The name of the secret in the specified Key Vault whose value is the passphrase for the Private Key | Enter the name of the Azure Key Vault secret that holds the value of the passphrase for the private key. |
-| The name of the secret in the specified Key Vault whose value is the Trust KeyStore Data | Enter the name of the Azure Key Vault secret that holds the value of the trust keystore data. Follow [Store the TLS/SSL certificate in the Key Vault](#store-the-tlsssl-certificate-in-the-key-vault) to upload the certificate to Azure Key Vault. |
-| The name of the secret in the specified Key Vault whose value is the passphrase for the Trust KeyStore | Enter the name of the Azure Key Vault secret that holds the value of the the passphrase for the trust keystore. |
-| The Trust KeyStore type (JKS,PKCS12) | Select the type of custom trust keystore. The supported values are JKS and PKCS12. |
-
 When you are satisfied with your selections, select **Next** and open **Load balancing** blade.
 
 ### Load balancing
@@ -193,7 +176,6 @@ You must select one of the following three options, each described in turn.
 
 * Generate a self-signed front-end certificate: Generate a self-signed front-end certificate and apply it during deployment.
 * Upload a TLS/SSL certificate: Upload the pre-signed certificate now.
-* Identify an Azure Key Vault: The Key Vault must already contain the certificate and its password stored as secrets.
 
 **Generate a self-signed frontend certificate**
 
@@ -210,16 +192,6 @@ You must select one of the following three options, each described in turn.
 | Confirm password | Re-enter the value of the preceding field. |
 | Trusted root certificate(.cer, .cert) | A trusted root certificate is required to allow back-end instances in the application gateway. The root certificate is a Base-64 encoded X.509(.CER) format root certificate. |
 
-**Identify an Azure Key Vault**
-
-| Field | Description |
-|-------|-------------|
-| Resource group name in current subscription containing the KeyVault | Enter the name of the Resource Group containing the Key Vault that stores the application gateway SSL certificate and the data required for SSL termination. |
-| Name of the Azure KeyVault containing secrets for the Certificate for SSL Termination | Enter the name of the Azure Key Vault that stores the application gateway SSL certificate and the data required for SSL termination. |
-| The name of the secret in the specified Key Vault whose value is the front-end TLS/SSL certificate data | Enter the name of the Azure Key Vault secret that holds the value of the Application Gateway front-end SSL certificate data. Follow [Store the TLS/SSL certificate in the Key Vault](#store-the-tlsssl-certificate-in-the-key-vault) to upload the certificate to Azure Key Vault. |
-| The name of the secret in the specified Key Vault whose value is the password for the front-end TLS/SSL certificate | Enter the name of the Azure Key Vault secret that holds the value of the password for the application gateway front-end SSL certificate. |
-| The name of the secret in the specified Key Vault whose value is the trusted root certificate data | A trusted root certificate is required to allow back-end instances in the application gateway. Enter the name of the Azure Key Vault secret that holds the value of the application gateway trusted root certificate data. Follow [Store the TLS/SSL certificate in the Key Vault](#store-the-tlsssl-certificate-in-the-key-vault) to upload the certificate to Azure Key Vault. |
-
 Regardless of how you provide the certificates, there are several other options when configuring the Application Gateway, as described next.
 
 | Field | Description |
@@ -389,27 +361,3 @@ After clicking **Create**, you will go to the **Deployment is in progress** page
 | `shellCmdtoOutputWlsImageProperties`|Shell command to display the base64 encoded string of the model properties.{{< line_break >}}Sample value:{{< line_break >}}`echo -e IyBDF...PTUK \| base64 -d > model.properties` |
 | `shellCmdtoOutputWlsVersionsandPatches` | Shell command to display the base64 encoded string of the WLS version and patches.{{< line_break >}}Sample value:{{< line_break >}}`echo -e CldlY...gMS4= \| base64 -d > version.info`|
 
-### Useful resources
-
-Review the following useful resources.
-
-#### Store the TLS/SSL certificate in the Key Vault
-
-1. Base 64 encode the certificate file; omit the `-w0` for macOS:
-
-    ```bash
-    base64 myIdentity.jks -w0 >mycert.txt
-    # base64 myIdentity.p12 -w0 >mycert.txt
-    # base64 myTrust.jks -w0 >mycert.txt
-    # base64 myTrust.p12 -w0 >mycert.txt
-    # base64 root.cert -w0 >mycert.txt
-    # base64 gatewayCert.pfx -w0 >mycert.txt
-    ```
-
-2. From the Azure portal, open your Key Vault.
-3. In the Settings section, select Secrets.
-4. Select Generate/Import.
-5. Under Upload options, leave the default value.
-6. Under Name, enter `myIdentityCertData`, or whatever name you like.
-7. Under Value, enter the content of the mycert.txt file.
-8. Leave the remaining values at their defaults and select Create.