Configuring the collection certificate store for the consumer binding on the application level

A collection certificate store is a collection of non-root, certificate authority (CA) certificates and certificate revocation lists (CRLs). This collection of CA certificates and CRLs is used to check for a valid signature in a digitally signed Simple Object Access Protocol (SOAP) message. Complete the following steps to configure a collection certificate for the consumer bindings on the application level:

  1. Locate the collection certificate store configuration panel in the WebSphere® Application Server administrative console.

    1. Click Applications > Enterprise applications > application_name.

    2. Under Related Items, click EJB Modules or Web Modules > URI_name.

    3. Under Additional properties, click Collection certificate store.

  2. Click New to create a collection certificate store configuration, click Delete to delete an existing configuration, or click the name of an existing collection certificate store configuration to edit its settings. If you are creating a new configuration, enter a name in the Certificate store name field.

    The name of the collection certificate store must be unique to the level of the application server. For example, if you create the collection certificate store for the application level, the store name must be unique to the application level. The name that is specified in the Certificate store name field is used by other configurations to refer to a predefined collection certificate store. WAS searches for the collection certificate store based on proximity.

    For example, if an application binding refers to a collection certificate store named cert1, the Application Server searches for cert1 at the application level before searching the server level.

  3. Specify a certificate store provider in the Certificate store provider field. WAS supports the IBMCertPath certificate store provider. To use another certificate store provider, you must define the provider implementation in the provider list within the install_dir/java/jre/lib/security/java.security file. However, make sure that your provider supports the same requirements of the certificate path algorithm as WAS.

  4. Click OK and Save to save the configuration.

  5. Click the name of your certificate store configuration. After you specify the certificate store provider, specify either the location of a certificate revocation list or the X.509 certificates. However, you can specify both a certificate revocation list and the X.509 certificates for your certificate store configuration.

  6. Under Additional properties, click Certificate revocation lists.

  7. Click New to specify a certificate revocation list path, click Delete to delete an existing list reference, or click the name of an existing reference to edit the path. You must specify the fully qualified path to the location where WAS can find your list of certificates that are not valid. For portability reasons, it is recommended that you use the WAS variables to specify a relative path to the certificate revocation lists (CRL). This recommendation is especially important when you are working in a WAS Network Deployment environment. For example, you might use the USER_INSTALL_ROOT variable to define a path such as $USER_INSTALL_ROOT/mycertstore/mycrl1. For a list of supported variables, click Environment > WebSphere variables in the WAS administrative console. The following list provides recommendation for using certificate revocation lists:

    • If CRLs are added to the collection certificate store, add the CRLs for the root certificate authority and each intermediate certificate, if applicable. When the CRL is in the certificate collection store, the certificate revocation status for every certificate in the chain is checked against the CRL of the issuer.

    • When the CRL file is updated, the new CRL does not take effect until you restart the Web service application.

    • Before a CRL expires, load a new CRL into the certificate collection store to replace the old CRL. An expired CRL in the collection certificate store results in a certificate path (CertPath) build failure.

  8. Click OK and Save to save the configuration.

  9. Return to the Collection certificate store configuration panel. See the first few steps of this article to locate the collection certificate store panel.

  10. Under Additional properties, click X.509 certificates.

  11. Click New to create a new configuration for X.509 certificates, click Delete to delete an existing configuration, or click the name of an existing X.509 certificate configuration to edit its settings. If you are creating a new configuration, enter a name in the Certificate store name field.

  12. Specify a path in the X.509 certificate path field. This entry is the absolute path to the location of the X.509 certificates. The collection certificate store is used to validate the certificate path of incoming X.509-formatted security tokens.

    You can use the USER_INSTALL_ROOT variable as part of the path name. For example, you might type: USER_INSTALL_ROOT/etc/ws-security/samples/intca2.cer. Do not use this certificate path for production use. You must obtain your own X.509 certificate from a certificate authority before putting your WAS environment into production.

    Click Environment > WebSphere variables in the WAS administrative console to configure the USER_INSTALL_ROOT variable.

  13. Click OK and then Save to save your configuration.

You have configured the collection certificate store for the consumer binding.

You must configure a token consumer configuration that references this certificate store configuration.

 

Related tasks

Configuring the collection certificate store for the generator binding on the application level