Before you begin
This article addresses the need to migration your security configurations from a previous release of IBM WebSphere Application Server to WebSphere Application Server, Version 5. Complete the following steps to migrate your security configurations:Why and when to perform this task
Steps for this task
Results
The security configuration of previous WebSphere Application Server releases and its applications are migrated to the new installation of WebSphere Application Server Version 5.Example
What to do next
After migration is complete, re-enable your security configurations with security disabled in the migrated version. You must re-enable your security configurations even if the previous version had security enabled.If custom user registry is used in the previous version, the migration process does not migrate the class files used by the custom user registry in the <previous_install_root>\classes directory. Therefore, after migration, copy your custom user registry implementation classes to the <install_root>\classes directory.
If you upgrade from WebSphere Application Server, Version 4.0.x to WebSphere Application Server, Version 5 or later, data associated with Version 4.0.x trust associations is not automatically migrated to Version 5 or later. To migrate trust associations, see Migrating trust association interceptors.