Thursday, March 24, 2011

Weblogic 10.3.5 Configuring SSL for SOA and OSB Serversin Weblogic

Weblogic 10.3.5 Configuring SSL for SOA and OSB Servers in Weblogic

By default, SSL is enabled and configured to use the demonstration Identity and Trust keystores. For testing and development purposes, the SSL configuration is complete. Use the steps in this section to configure SSL for production use.
To configure SSL:
  1. Expand the Servers node.
  2. Select the name of the server for which you want to configure keystores (for example, exampleserver).

  1. Select the Configuration-->Keystores and SSL tab.
  2. Information about the demonstration Identity and Trust keystores is displayed in the Keystore Configuration.

  3. Configure new Identity and Trust keystores for WebLogic Server.  

 
  1. Click the Change... link in the SSL Configuration to configure attributes for SSL.
  2. The Configure SSL page appears.

  3. Specify how the identity and trust for WebLogic Server is stored. The following options are available:

    • Key Stores—Use this option if you created Identity and Trust keystores for WebLogic Server. If you choose this option, go to step 8.
    • Files or Key Store Providers—Use this option if you stored private keys and trusted CA certificates in a file or in a JKS keystore accessed via the WebLogic Keystore provider (as supported in previous releases of WebLogic Server). If you choose this option, go to step 9. This option is available for the purpose of backward compatibility only and it automatcally set with security information from a previous release of WebLogic Server.

  4. Click Continue.


  5. Specify the alias used to load the private key into the keystore in the Private Key Alias and the password used to retrieve the private key from the keystore in the Passphrase attibute. You may have specified this information when creating the Identity keystore; however, for the purpose of SSL configuration specify the information again. Skip to step 10.

 

  1. Specify information about the location of identity and trust for WebLogic Server.
  2. Note: This step only applies if the Files or Key Store Providers option is specified.
    • Private Key File Name—The directory location of the private key for WebLogic Server. Specify a value for this attribute only if you stored the private key for WebLogic Server in a file (versus a WebLogic Keystore provider).
    • Private Key Alias—The alias specified when loading the private key for WebLogic Server from the keystore. Specify a value for this field only if you stored the private key for WebLogic Server in a keystore accessed by the WebLogic Keystore provider.
    • Passphrase—The password specified when loading the private key for WebLogic Server into the keystore. Specify a value for this field only if you stored the private key for WebLogic Server in a keystore accesssed by the WebLogic Keystore provider. Confirm the password. If you protected the private key file with a password, specify the weblogic.management.pkpassword command-line argument when starting the server.
    • Server Certificate File Name— The directory location of the digital certificate for WebLogic Server. If you are using a certificate chain that is deeper than two certificates, you to need to include the entire chain in PEM format in the certificate file.
    • Trusted CA File Name—The name of the file containing the PEM-encoded trusted certificate authorities.
  3. Click Continue.
  4. Click Finish.
  5. Reboot WebLogic Server.

Amazon Bedrock and AWS Rekognition comparison for Image Recognition

 Both Amazon Bedrock and AWS Rekognition are services provided by AWS, but they cater to different use cases, especially when it comes to ...