This following sections describe how to configure identity and trust for WebLogic Server:
Before performing the steps in this chapter, review the "Identity and Trust" section in Understanding Security for Oracle WebLogic Server.
Private keys, digital certificates, and trusted certificate authorities establish and verify server identity and trust.
SSL uses public key encryption technology for authentication. With public key encryption, a public key and a private key are generated for a server. Data encrypted with the public key can only be decrypted using the corresponding private key and data encrypted with the private key can only be decrypted using the corresponding public key. The private key is carefully protected so that only the owner can decrypt messages that were encrypted using the public key.
The public key is embedded in a digital certificate with additional information describing the owner of the public key, such as name, street address, and e-mail address. A private key and digital certificate provide identity for the server.
The data embedded in a digital certificate is verified by a certificate authority and digitally signed with the certificate authority's digital certificate. Well-know certificate authorities include Verisign and Entrust.net. The trusted certificate authority (CA) certificate establishes trust for a certificate.
An application participating in an SSL connection is authenticated when the other party evaluates and accepts the application's digital certificate. Web browsers, servers, and other SSL-enabled applications generally accept as genuine any digital certificate that is signed by a trusted certificate authority and is otherwise valid. For example, a digital certificate can be invalidated because it has expired or the digital certificate of the certificate authority used to sign it expired. A server certificate can be invalidated if the host name in the digital certificate of the server does not match the URL specified by the client.
To create identity and trust for a server:
Obtain digital certificates, private keys, and trusted CA certificates from the CertGen utility, Sun Microsystem's keytool utility, or a reputable vendor such as Entrust or Verisign. You can also use the digital certificates, private keys, and trusted CA certificates provided by the WebLogic Server kit. The demonstration digital certificates, private keys, and trusted CA certificates should be used in a development environment only.
Store the private keys, digital certificates, and trusted CA certificates. Private keys and trusted CA certificates are stored in a keystore.
Note:The preferred keystore format is JKS (Java KeyStore). WebLogic Server supports private keys and trusted CA certificates stored in files or in the WebLogic Keystore provider for the purpose of backward compatibility only.
Configure the identity and trust keystores for WebLogic Server in the WebLogic Server Administration Console. See "Configure keystores" in the Oracle WebLogic Server Administration Console Help.
The remaining sections describe these steps.
The PEM (Privacy Enhanced Mail) format is the preferred format for private keys, digital certificates, and trusted certificate authorities (CAs). The preferred keystore format is the JKS (Java KeyStore) format.
.pem format file begins with this line:
and ends with this line:
.pem format file supports multiple digital certificates (for example, a certificate chain can be included). The order of certificates within the file is important. The server's digital certificate should be the first digital certificate in the file, followed by the issuer certificate, and so on. Each certificate in the chain is followed by its issuer certificate. If the last certificate in the chain is the self-signed (self-issued) root certificate of the chain, the chain is considered complete. Note that the chain does not have to be complete.
When using the deprecated file-based private keys, digital certificates, and trusted CAs, WebLogic Server can use digital certificates in either PEM or distinguished encoding rules (DER) format.
.der format file contains binary data for a single certificate. Thus, a
.der file can be used only for a single certificate, while a
.pem file can be used for multiple certificates.
Microsoft is often used as a certificate authority. Microsoft issues trusted CA certificates in p7b format, which must be converted to PEM before they can be used with WebLogic Server. For more information, see Converting a Microsoft p7b Format to PEM Format.
Private key files (meaning private keys not stored in a keystore) must be in PKCS#5/PKCS#8 PEM format.
You can still use private keys and digital certificates used with other versions of WebLogic Server with this version of WebLogic Server. Convert the private key and digital certificate from distinguished encoding rules (DER) format to privacy-enhanced mail (PEM) format. For more information, see the description of the "der2pem" utility in "Using the WebLogic Server Java Utilities" in Command Reference for Oracle WebLogic Server.
After converting the files, ensure the digital certificate file has the
-----BEGIN CERTIFICATE----- header and the
-----END CERTIFICATE----- footer. Otherwise, the digital certificate will not work.
Note:OpenSSL can add a header to the PEM certificate it generates. In order to use such certificates with WebLogic Server, everything in front of "
-----BEGIN CERTIFICATE-----" should be removed from the certificate, which you can do with a text editor.
Servers need a private key, a digital certificate containing the matching public key, and a certificate for at least one trusted certificate authority. WebLogic Server supports private keys, digital certificates, and trusted CA certificates from the following sources:
The demonstration digital certificates, private keys, and trusted CA certificates in the
\server\lib directory and the
The demonstration digital certificates, private keys, and trusted CA certificates should be used in a development environment only.
Sun Microsystem's keytool utility can also be used to generate a private key, a self-signed digital certificate for WebLogic Server, and a Certificate Signing Request (CSR).
Submit the CSR to a certificate authority to obtain a digital certificate for WebLogic Server.
Use the keytool utility to update the self-signed digital certificate with a new digital certificate.
Use the keytool utility to obtain trust and identity when using WebLogic Server in a production environment.
For more information about Sun's keytool utility, see the keytool-Key and Certificate Management Tool description at
Note:When you use the keytool utility, the default key pair generation algorithm is Digital Signature Algorithm (DSA). WebLogic Server does not support DSA. Specify another key pair generation and signature algorithm when using WebLogic Server.
The CertGen utility generates digital certificates and private keys that should be used only for demonstration or testing purposes in a development environment, and not in a production environment. Use the CertGen utility if you want to set an expiration date in the digital certificate or specify a correct host name in the digital certificate so that you can use host name verification. (The demonstration digital certificate provided by WebLogic Server uses the machine's default host name as the host name.) For more information about using the CertGen utility to obtain private keys and digital certificates, see Using the CertGen Utility.
Note:The Certificate Request Generator servlet is deprecated. Use the keytool utility from Sun Microsystems in place of the Certificate Request Generator servlet. For more information about keytool, see Common Keytool Commands.
Table 11-1 lists keytool commands you use when creating and using JKS keystores with WebLogic Server.
Note:The keytool utility is a product of Sun Microsystems. Therefore, Oracle does not provide complete documentation on the utility. For more information, see the keytool-Key and Certificate Management Tool description at
keytoolcommand includes parameters for specifying passwords, you should never include unencrypted passwords in command lines. Instead, you should allow
keytoolto prompt you for the password after you enter the command, as in the following example. User input is shown in bold.
C:\DOMAIN_NAME>keytool -genkey -keystore MyKeyStore Enter keystore password: Re-enter new password:
Note that passwords are not echoed in the command window when entered in response to prompts, which allows for secure password input.
keytool -genkey -keystore keystorename
Generates a new private key entry and self-signed digital certificate in a keystore. If the keystore does not exist, it is created.
keytool -import -alias aliasforprivatekey -file privatekeyfilename.pem -keyfilepass privatekeypassword -keystore keystorename -storepass keystorepassword
Updates the self-signed digital certificate with one signed by a trusted CA.
keytool -import -alias rootCA -trustcacerts -file RootCA.pem -keystore trust.jks -storepass keystorepassword
keytool -import -alias intermediate -trustcacerts -file Intermediate.pem -keystore keystorename -storepass keystorepassword
Creates a custom keystore to be used for holding an intermediate CA certificate.
This enables WebLogic Server's SSL implementation to transmit the intermediate certificate with the server's public certificate to the client during the SSL handshake.
keytool -import -alias aliasfortrustedca -trustcacerts -file trustedcafilename.pem -keystore keystorename -storepass keystorepassword
Loads a trusted CA certificate into a keystore. If the keystore does not exist, it is created.
keytool -certreq -alias alias -sigalg sigalg -file certreq_file -keyfilepass privatekeypassword -storetype keystoretype -keystore keystorename -storepass keystorepassword
Generates a Certificate Signing Request (CSR), using the PKCS#10 format, and a self-signed certificate with a private key.
Stores the CSR in the specified
keytool -list -keystore keystorename
Displays what is in the keystore.
keytool -delete -keystore keystorename
-storepass keystorepassword -alias privatekeyalias
Deletes the entry identified by the specified alias from the keystore.
Provides online help for keytool.
Note:The CertGen utility generates digital certificates and private keys that should only be used for demonstration or testing purposes, not in a production environment. For important information about limitations on its use, see Limitation on CertGen Usage.
The CertGen utility provides command line options to specify a CA certificate and key to be used for issuing generated certificates. The digital certificates generated by the CertGen utility by default have only the host name of the machine on which they were generated, and not the fully-qualified DNS name, as the value for its common name field (cn). Command line options let you specify values for the cn and other Subject domain name (DN) fields, such as
The CertGen utility generates public certificate and private key files in PEM and DER formats. On Windows, double-click
.der files to view the details of the generated digital certificate. The
.pem files can be used when you boot WebLogic Server or use the digital certificates with a client.
By default, the CertGen utility uses the following demonstration digital certificate and private-key files:
CertGenCAKey.der. CertGen looks for these files in the current directory, or in the
/server/lib directory, as specified in the
weblogic.home system property or the
CLASSPATH. If you want to use these files, you need not specify CA files on the command line. Alternatively, you can specify CA files on the command line.
For information about the CertGen utility's syntax and arguments, see "CertGen" in the Command Reference for Oracle WebLogic Server.
For an example that generates a certificate and private key using the CertGen utility, and then creates a keystore and stores a private key using the ImportPrivateKey utility, see "ImportPrivateKey" in the Command Reference for Oracle WebLogic Server.
Note:If you do not explicitly specify a hostname with the -cn option, CertGen uses the JDK
InetAddress.getHostname()method to get the hostname that it puts in the Subject common name. The
getHostName()method works differently on different platforms. It returns a fully qualified domain name (FQDN) on some platforms (for example, Solaris) and a short host name on other platforms (for example, Windows NT). On Solaris, the result of
InetAddress.getHostname()depends on how the hosts entry is configured in the
If WebLogic Server is acting as a client (and by default host name verification is enabled), you need to ensure that the host name specified in the URL matches the Subject common name in the server certificate. Otherwise, connections will fail because the host names do not match.
By default, WebLogic Server is installed and configured with the
DemoIdentity.jks keystore, which contains a demonstration public certificate and private key for WebLogic Server. This certificate and key are created by CertGen with the default options of containing only the host name in the common name field (cn), and not the fully-qualified DNS name. As a result, attempts to establish SSL connections may fail in some situations due to a host name verification exception. This section describes this limitation and provides some workarounds.
If you are using the demo certificates in a multi-server domain, Managed Server instances will fail to boot if they cannot establish an SSL connection with the Administration Server. An error message similar to the following may be generated:
BAD_CERTIFICATE alert was received from node-name.oracle.com - xxx.yy.zzz.yyy. Check the peer to determine why it rejected the certificate chain (trusted CA configuration, hostname verification). SSL debug tracing may be required to determine the exact reason the certificate was rejected.
This error occurs because the host name verifier, which is enabled by default in all WebLogic domains and which is used during the SSL handshake, compares the value of the cn field in the certificate with the fully-qualified DNS name of the SSL server that accepts the SSL connection. If these names do not match, the SSL connection is dropped.
If you use the demo identity certificates in a WebLogic domain, you can use the following workarounds:
Specify the SSL listen address of each WebLogic Server instance in a domain as the host name that appears in the certificate's cn field. Avoid using the fully-qualified DNS name or IP address. This workaround consists of two steps:
When using the Configuration Wizard to create the WebLogic domain, specify the listen address of each WebLogic Server instance as a simple host name as it appears in the certificate's cn field, not as a fully-qualified DNS name or IP address. For example, if the host name in the certificate is
avitek01, the listen address for the server instance should be specified simply as
At run time, when specifying the SSL listen address of a server instance, make sure the URL also matches the host name for that server as specified as the certificate's cn field. For example:
To start a Managed Server instance, pass the URL of the Administration Server's SSL listening address as a parameter to the
startManagedWebLogic script. The URL should be specified in a form that excludes the domain suffix. For example:
C:\mydomain\bin> startManagedWebLogic.cmd https://admin01:7002
Disable host name verification. This causes WebLogic Server to skip the verification check of ensuring that the host name in the URL to which a connection is made matches the host name in the digital certificate that the server sends back as part of the SSL connection.
You can disable host name verification by including a command similar to the following in the setDomainEnv script:
set JAVA_OPTIONS=%JAVA_OPTIONS% -Dweblogic.security.SSL.ignoreHostnameVerification=true
For information about configuring host name verification, see Using Host Name Verification.
Note:Oracle does not recommend using the demo certificates or turning off host name verification in a production environment.
Many companies act as their own certificate authority. To use those trusted CA certificates with WebLogic Server:
Ensure the trusted CA certificates are in PEM format.
If the trusted CA certificate is in DER format, use the der2pem utility to convert them.
If the trusted CA certificate was issued by Microsoft, see Converting a Microsoft p7b Format to PEM Format.
If the trusted CA certificate has a custom file type, use the steps in Converting a Microsoft p7b Format to PEM Format, to convert the trusted CA certificate to PEM format.
Create a trust keystore. For more information, see How WebLogic Server Locates Trust.
Store the trusted CA certificate in the trust keystore. For more information, see How WebLogic Server Locates Trust.
Configure WebLogic Server to use the trust keystore. For more information, see Configuring Keystores for Production.
Digital certificates issued by Microsoft are in a format (p7b) that cannot be used by WebLogic Server. The following example converts a digital certificate in p7b (PKCS#7) format to PEM format on Windows XP:
In Windows Explorer, select the file (
.p7b) you want to convert. Double-click on the file to display a Certificates window.
In the left pane of the Certificates window, expand the file.
Expand the Certificates folder to display a list of certificates.
Select a certificate to convert to PEM format. Right-click on the certificate, then choose All Tasks > Export to display the Certificate Export Wizard.
In the wizard, click Next.
Base-64 encoded X.509 (
.CER) option. Then click Next. (
Base-64 encoded is the PEM format.)
In the File name field, enter a name for the converted digital certificate; then click Next.
Note:The wizard appends a
.cerextension to the output file. The
.cerextension is a generic extension which is appended to both base-64 encoded certificates and DER certificates. You can change the extension to
.pemafter you exit the wizard.
Verify that the settings are correct. If the settings are correct, click Finish; if they are not correct, click Back and make any necessary modifications.
Note:For p7b certificate files that contain certificate chains, you need to concatenate the issuer PEM digital certificates to the certificate file. The resulting certificate file can be used by WebLogic Server.
Low-security browser certificates are easy to acquire and can be done from within the Web browser, usually by selecting the Security menu item in Options or Preferences. Go to the Personal Certificates item and ask to obtain a new digital certificate. You will be asked for some information about yourself.
The digital certificate you receive contains public information, including your name and public key, and additional information you would like authenticated by a third party, such as your E-mail address. Later you will present the digital certificate when authentication is requested.
As part of the process of acquiring a digital certificate, the Web browser generates a public-private key pair. The private key should remain secret. It is stored on the local file system and should never leave the Web browser's machine, to ensure that the process of acquiring a digital certificate is itself safe. With some browsers, the private key can be encrypted using a password, which is not stored. When you encrypt your private key, you will be asked by the Web browser for your password at least once per session.
Note:Digital certificates obtained from Web browsers do not work with other types of Web browsers or on different versions of the same Web browser.
Note:The use of file-based certificate chains is deprecated. Now the whole certificate chain is imported into a keystore. The steps in this section are provided for the purpose of backward compatibility only.
To use certificate chains with WebLogic Server:
Ensure that all the digital certificates are in PEM format. If they are in DER format, you can convert them using the "der2pem" utility. If you are using a digital certificate issued by Microsoft, see Converting a Microsoft p7b Format to PEM Format. You can use the steps in the section to convert other types of digital certificates. Save the digital certificate in Base 64 format.
Open a text editor and include all the digital certificate files into a single file. The order is important. The server digital certificate should be the first digital certificate in the file. The issuer of that digital certificate should be the next in the file and so on until you get to the self-signed root certificate authority certificate. This digital certificate should be the last certificate in the file.
You cannot have blank lines between digital certificates.
Specify the file in the Server Certificate File Name field on the Configuration > SSL page in the WebLogic Server Administration Console.
Example 11-1 shows a sample certificate chain.
-----BEGIN CERTIFICATE----- MIICyzCCAjSgAwIBAgIBLDANBgkqhkiG9w0BAQQFADCBtjELMAkGA1UEBhMCVVMxEzARBgNVBAgTCkNhbGlmb3JuaWExFjAUB gNVBAcTDVNhbiBGcmFuY2lzY28xFTATBgNVBAoTDEJFQSBXZWJMb2dpYzERMA8GA1UECxMIU2VjdXJpdHkxLzAtBgNVBAMTJk RlbW8gQ2VydGlmaWNhdGUgQXV0aG9yaXR5IENvbnN0cmFpbnRzMR8wHQYJKoZIhvcNAQkBFhBzZWN1cml0eUBiZWEuY29tMB4 XDTAyMTEwMTIwMDIxMloXDTA2MTAxNTIwMDIxMlowgZ8xCzAJBgNVBAYTAlVTMRMwEQYDVQQIEwpDYWxpZm9ybmlhMRYwFAYD VQQHEw1TYW4gRnJhbmNpc2NvMRUwEwYDVQQKEwxCRUEgV2ViTG9naWMxETAPBgNVBAsTCFNlY3VyaXR5MRkwFwYDVQQDExB3Z WJsb2dpYy5iZWEuY29tMR4wHAYJKoZIhvcNAQkBFg9zdXBwb3J0QGJlYS5jb20wgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAo GBAMJX8nKUgsFej8pEu/1IVcHUkwY0c2JbBzOryu3sce4QjX+rGxiCjoPm2MY=yts2BvonuJ6CztdZf8B/LBEWCz+qRrtdFn9 mKSZWGvrAkmMPz2RhXEOThpoRo5kZz2FQ9XF/PxIJXTYCM7yooRBwXoKYjquRwiZNtUiU9kYi6Z3prAgMBAAEwDQYJKoZIhvc NAQEEBQADgYEAh2eqQGxEMUnNTwEUD 0tBq+7YuAkjecEocGXvi2G4YSoWVLgnVzJoJuds3c35KE6sxBe1luJQuQkE9SzALG/6lDIJ5ctPsHFmZzZxY7scLl6hWj5ON8 oN2YTh5Jo/ryqjvnZvqiNIWe/gqr2GLIkajC0mz4un1LiYORPig3fBMH0= -----END CERTIFICATE----- -----BEGIN CERTIFICATE----- MIIC+jCCAmOgAwIBAgIBADANBgkqhkiG9w0BAQQFADCBtjELMAkGA1UEBhMCVVMxEzARBgNVBAgTCkNhbGlmb3JuaWExFjAUB gNVBAcTDVNhbiBGcmFuY2lzY28xFTATBgNVBAoTDEJFQSBXZWJMb2dpYzERMA8GA1UECxMIU2VjdXJpdHkxLzAtBgNVBAMTJk RlbW8gQ2VydGlmaWNhdGUgQXV0aG9yaXR5IENvbnN0cmFpbnRzMR8wHQYJKoZIhvcNAQkBFhBzZWN1cml0eUBiZWEuY29tMB4 XDTAyMTEwMTIwMDIxMVoXDTA2MTAxNjIwMDIxMVowgbYxCzAJBgNVBAYTAlVTMRMwEQYDVQQIEwpDYWxpZm9ybmlhMRYwFAYD VQQHEw1TYW4gRnJhbmNpc2NvMRUwEwYDVQQKEwxCRUEgV2ViTG9naWMxETAPBgNVBAsTCFNlY3VyaXR5MS8wLQYDVQQDEyZEZ W1vIENlcnRpZmljYXRlIEF1dGhvcml0eSBDb25zdHJhaW50czEfMB0GCSqGSIb3DQEJARYQc2VjdXJpdHlAYmVhLmNvbTCBnz ANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEA3ynD8l5JfLob4g6d94dNtI0Eep6QNl9bblmswnrjIYz1BVjjRjNVal9fRs+8jvm 85kIWlerKzIMJgiNsj50WlXzNX6orszggSsW15pqV0aYE9Re9K CNNnORlsLjmRhuVxg9rJFEtjHMjrSYr2IDFhcdwPgIt0meWEVnKNObSFYcCAwEAAaMWMBQwEgYDVR0TAQH/BAgwBgEB/wIBAT ANBgkqhkiG9w0BAQQFAAOBgQBS+0oqWxGyqbZO028zf9tQT2RKojfuwywrDoGW96Un5IqpFnBHIu5atliJo3OUpiH18KkwLN8 DVP/3t3K3O3kXdIuLbqAL0i5xyBlAhr7gE5eVhIyeMg7ETBPLyGO2BF13Y24LlsO+MX9jW7fxMraPN608QeJXkZw0E0cGwrw2AQ== -----END CERTIFICATE-----
Once you have obtained private keys, digital certificates, and trusted CA certificates, you need to store them so that WebLogic Server can use them to find and verify identity. Private keys, their associated digital certificates, and trusted CA certificates are stored in keystores. The keystores can be configured through the WebLogic Server Administration Console or specified on the command line. Use the Configuration > Keystore page in the WebLogic Server Administration Console to configure identity and trust keystores for WebLogic Server. See "Configure keystores" in the Oracle WebLogic Server Administration Console Help.
For the purpose of backward compatibility, private keys and trusted CA certificates can be stored in a file or in a JKS keystore accessed via the WebLogic Keystore provider. In addition, trusted CA certificates can be stored in a JKS keystore. Use the Configuration > SSL page of the WebLogic Server Administration Console to specify identity and trust options when using a file or a JKS keystore accessed via the WebLogic Keystore provider.
When you configure SSL, you have to decide how identity and trust will be stored. Although one keystore can be used for both identity and trust, Oracle recommends using separate keystores for both identity and trust because the identity keystore (private key/digital certificate pairs) and the trust keystore (trusted CA certificates) may have different security requirements. For example:
For trust, you only have to put the certificates (non-sensitive data) in the keystore while for identity, you have to put the certificate and private key (sensitive data) in the keystore.
The identity keystore may be prohibited by company policy from ever being put in the network while the trust keystore can be distributed over the network.
The identity keystore may be protected by the operating system for both reading and writing by non-authorized users while the trust keystore only needs to be write protected.
The identity keystore password is generally known to fewer people than the password for the trust keystore.
In general, systems within a domain have the same trust rules (use the same set of trusted CAs), while they tend to have per-server identity. Identity requires a private key, and private keys should not be copied from one system to another. Therefore, you should maintain separate identity keystores for each system, each keystore containing only the server identity needed for that system. However, trust keystores can be copied from system to system; thus making it easier to standardize trust rules.
Identity is more likely to be stored in hardware keystores such as nCipher. Trust can be stored in a file-based JDK keystore without having security issues because a trust store contains only certificates, not private keys.
A keystore is for the secure storage and management of private keys/digital certificate pairs and trusted CA certificates. Use the following mechanisms to create a keystore and load private keys and trusted CA certificates into the keystore:
The WebLogic ImportPrivateKey utility. The ImportPrivateKey utility allows you to take private key and digital certificate files and load them into a keystore. For more information, see "ImportPrivateKey" in the Command Reference for Oracle WebLogic Server.
Sun Microsystem's keytool utility. Use the keytool utility to generate a private key/digital certificate pair and then import the signed private key into the keystore. For more information, see How WebLogic Server Locates Trust. While you can use the keytool utility to generate new private keys and digital certificates and add them to a keystore, the utility does not allow you to take an existing private key from a file and import it into the keystore. Instead, use the WebLogic ImportPrivateKey utility.
Note:The keytool utility does allow you to import trusted CA certificates from a file into a keystore.
Custom utilities. WebLogic Server can use keystores created with custom tools or utilities. How to create and use these utilities is outside the scope of this document.
All private key entries in a keystore are accessed by WebLogic Server via unique aliases. You specify the alias when loading the private key into the keystore. Aliases are case-insensitive; the aliases Hugo and hugo would refer to the same keystore entry. Aliases for private keys are specified in the Private Key Alias field on the Configuration > SSL page in the WebLogic Server Administration Console. Although WebLogic Server does not use the alias to access trusted CA certificates, the keystore does require an alias when loading a trusted CA certificate into the keystore.
All certificate authorities in a keystore identified as trusted by WebLogic Server are trusted.
To use SSL in development mode between a client such as Eclipse and WebLogic Server, configure the demo certificates in the JVM for both the client and the server:
/wlserver_10.3/server/lib/cacerts to the
jre/lib/security directory of the client's JVM. For example, if you are using Eclipse with its default JDK, copy
/wlserver_10.3/server/lib/cacerts to the
jre/lib/security directory of the WebLogic Server's JVM. For a domain using JRockit, copy
Restart both WebLogic Server and the client.
As an alternative, you can import the certificates, rather than copying the
WebLogic Server uses the following algorithm when it loads its trusted CA certificates:
If the keystore is specified by the
-Dweblogic.security.SSL.trustedCAkeystore command-line argument, load the trusted CA certificates from that keystore.
Else if the keystore is specified in the configuration file (
config.xml), load trusted CA certificates from the specified keystore. If the server is configured with DemoTrust, trusted CA certificates will be loaded from the
\server\lib\DemoTrust.jks and the JDK
Else if the trusted CA file is specified in the configuration file (
config.xml), load trusted CA certificates from that file (this is only for compatibility with 6.x SSL configurations).
Else load trusted CA certificates from
By default, WebLogic Server is configured with two keystores:
DemoIdentity.jks—Contains a demonstration private key for WebLogic Server. This keystore contains the identity for WebLogic Server.
DemoTrust.jks—Contains the trusted certificate authorities from the
\server\lib\DemoTrust.jks and the JDK
cacerts keystores. This keystore establishes trust for WebLogic Server.
These keystores are located in the
\server\lib directory. For testing and development purposes, the keystore configuration is complete. However, do not use the demonstration keystores in a production environment. Because the digital certificates and trusted CA certificates in the demonstration keystores are signed by a WebLogic Server demonstration certificate authority, a WebLogic Server installation using the demonstration keystores will trust any WebLogic Server installation that also uses the demonstration keystores. You want to create a secure environment where only your installations trust each other.
To configure keystores for use in a production environment:
Obtain private keys and digital certificates from a reputable certificate authority such as Verisign, Inc. or Entrust.net. See Obtaining Private Keys, Digital Certificates, and Trusted Certificate Authorities.
Create identity and trust keystores. See Creating a Keystore and Loading Private Keys and Trusted Certificate Authorities into the Keystore.
Load the private keys and trusted CAs into the identity and trust keystores. See Creating a Keystore and Loading Private Keys and Trusted Certificate Authorities into the Keystore.
Use the WebLogic Server Administration Console to configure the identity and trust keystores. See "Configure keystores" in the Oracle WebLogic Server Administration Console Help.
You can also use the WebLogic Scripting Tool or Java Management Extensions (JMX) APIs to create a new security configuration. For more information see the Oracle WebLogic Scripting Tool and Developing Custom Management Utilities With JMX for Oracle WebLogic Server manuals.
WebLogic Server provides a means to examine details about information passed by an end user issuing a request to determine whether authentication should succeed or fail. The details may include the end user's certificate, Subject, and IP address. This capability is provided by the
weblogic.security.SSL.CertificateCallback interface, which you can implement to create a certificate callback handler. When configured with WebLogic Server, this callback handler is invoked automatically whenever a client request is received over a secure RMI connection; for example, one that uses the T3s or IIOPS protocols.
To configure a certificate callback handler so that it is in effect for all secure inbound RMI connections, you define it as a WebLogic Server system property that is passed in the server startup command.
The following topics describe how a certificate callback handler works and how to implement and configure one:
When a client makes a secure RMI connection to a WebLogic Server instance that is configured with a certificate callback handler, WebLogic Server invokes the callback handler. The callback evaluates details about the end user that are contained in the connection request, then returns a boolean value indicating whether authentication is successful.
The CertificateCallback interface calls the
validate method on an
CertificateCallbackInfo instance, which contains methods to obtain the following information from the end user that is contained in the RMI connection request:
Client host name, IP address, and port
Client domain name
Destination host name, IP address, and port
The callback implementation includes the logic that evaluates the client data that is obtained and returns
false as follows:
If the callback returns
true, authentication succeeds and the client connection to WebLogic Server is made.
If the callback returns
false, a RemoteException is thrown containing the "Authentication denied" message.
Note:If you use a certificate callback implementation in WebLogic Server, a callback is generated whenever a request is received over a secure port. As a result, using certificate callbacks may impose a performance overhead that should be taken into consideration.
weblogic.security.SSL.CertificateCallback interface contains a single invocation on the
validate method on a
weblogic.security.SSL.CertificateCallbackInfo instance. The CertificateCallbackInfo instance contains methods to obtain details about the end user that are passed over the secure RMI connection.
You implement logic that evaluates the data that is returned and returns a
false. The logic does not need to evaluate all data that is returned. Typically, only the certificate is evaluated; for example, obtaining the common name (cn) or distinguished name (dn).
For more information, see the following Javadoc in the Oracle WebLogic Server API Reference:
To configure the callback with WebLogic Server, specify the callback implementation as a system property in the WebLogic Server start command. The property should point to the callback implementation class that is on the server's classpath. For example, if the callback implementation class is
MyCertificateCallback.java in the package
MyCertificateCallback.class is in the server's classpath, the following command sets the callback implementation property in WebLogic Server:
java weblogic.Server -Dweblogic.security.SSL.CertificateCallback=com.mycompany.security.MyCertificateCallback
Note that if WebLogic Server is configured for one-way SSL, a client certificate is never sent to the server. Oracle recommends using certificate callbacks handlers only when WebLogic Server is configured for two-way SSL. For more information, see Chapter 12, "Configuring SSL."