Use this topic to migrate the security configuration of previous WebSphere Application Server releases and its applications to the new installation of WebSphere Application Server.
This information addresses the need to migrate your security configurations from a previous release of IBM WebSphere Application Server to WebSphere Application Server Version 6.1 or later. Complete the following steps to migrate your security configurations:
The security configuration of previous WebSphere Application Server releases and its applications are migrated to the new installation of WebSphere Application Server Version 6.1.
If a custom user registry is used in the previous version, the migration process does not migrate the class files that are used by the standalone custom registry in the previous app_server_root/classes directory. Therefore, after migration, copy your custom user registry implementation classes to the app_server_root/classes directory.
If you upgrade from WebSphere Application Server, Version 5.x to WebSphere Application Server, Version 6.1, the data that is associated with Version 5.x trust associations is not automatically migrated to Version 6.1. To migrate trust associations, see Migrating trust association interceptors.
If the previous version instance is configured
to enable secure connections using digital certificates that are signed by
the Digital Certificate Manager (DCM) local certificate authority, those certificates
must be renewed. For example, they must be renewed for the previous version
instance, the WebSphere Application Server Version 6.1 profile,
and all of the Secure Socket Layer-enabled clients and servers that connect
to WebSphere Application Server. For more information, see SSL handshake failure using digital certificates signed by
a Digital Certificate Manager (DCM) local certificate authority.
Vender-specific signer certificates, such as VeriSign and Thawte, are no longer included in the default truststore for WebSphere Application Server. To have these signer certificates available after migration, you must import them into the Application Server. To import signer certificates using the administration console, navigate to
. i5/OS
*SYSTEM certificate stores for applications are deprecated in WebSphere Application
Server Version 5. In WebSphere Application Server, you must migrate your applications
to use Java keystores.
The os400.security.password.validation.list.object
property is profile-dependent. If you are migrating from Version 5, see Migrating Java thin clients that use the password encoding algorithm for instructions on how to migrate
your client configuration.
For WebSphere Application Server Version 6.1.x, the default keystore type has changed from JKS to PKCS12. If the keystore Types are not changed to PKCS12 after the migration. you may encounter errors when accessing the keystore. The Type can be changed to PKCS12 using the administrative console. To change the Type, click Security > SSL certificate and key management > Manage endpoint security configurations > {Inbound | Outbound SSL_configuration_name}. Under Related Items, click Key stores and certificates and then the name of a specific keystore to show the details of that keystore. From this keystore details panel, change the Type to be PKCS12.
In this information ...Subtopics
Related concepts
| IBM Redbooks, demos, education, and more |