Migration Concepts Security Data Migration

Design Considerations 3-17 ■ Moving from one security realm to a new security realm in the same WebLogic Server domain, where one or more of the WebLogic security providers will be replaced with custom security providers. In this case, administrators need to copy security data for the security providers that are not being replaced. The following sections provide more information about security data migration: ■ Section 3.4.1, Migration Concepts ■ Section 3.4.2, Adding Migration Support to Your Custom Security Providers ■ Section 3.4.3, Administration Console Support for Security Data Migration

3.4.1 Migration Concepts

Before you start to work with security data migration, you need to understand the following concepts: ■ Section 3.4.1.1, Formats ■ Section 3.4.1.2, Constraints ■ Section 3.4.1.3, Migration Files

3.4.1.1 Formats

A format is simply a data format that specifies how security data should be exported or imported. Currently, WebLogic Server does not provide any standard, public formats for developers of security providers. Therefore, the format you use is entirely up to you. Keep in mind, however, that for data to be exported from one security provider and later imported to another security provider, both security providers must understand how to process the same format. Supported formats are the list of data formats that a given security provider understands how to process.

3.4.1.2 Constraints

Constraints are keyvalue pairs used to specify options to the export or import process. Constraints allow administrators to control which security data is exported or imported from the security providers database. For example, an administrator may want to export only users not groups from an Authentication providers database, or a subset of those users. Supported constraints are the list of constraints that administrators may specify during the migration process for a particular security provider. For example, an Authentication providers database can be used to import users and groups, but not security policies.

3.4.1.3 Migration Files

Export files are the files to which security data is written in the specified format during the export portion of the migration process. Import files are the files from which security data is read also in the specified format during the import portion of the migration process. Both export and import files are simply temporary storage Note: Because the data format used for the WebLogic security providers is unpublished, you cannot currently migrate security data from a WebLogic security provider to a custom security provider, or visa versa. Additionally, security vendors wanting to exchange security data with security providers from other vendors will need to collaborate on a standard format to do so. 3-18 Developing Security Providers for Oracle WebLogic Server locations for security data as it is migrated from one security providers database to another.

3.4.2 Adding Migration Support to Your Custom Security Providers