Review the descriptions of the WebLogic security providers to determine whether Determine which type of custom security provider you want to create. Identify which security service provider interfaces SSPIs you must implement to Decide whether you will im

2-2 Developing Security Providers for Oracle WebLogic Server

2.2.1 Designing the Custom Security Provider

The design process includes the following steps:

1. Review the descriptions of the WebLogic security providers to determine whether

you need to create a custom security provider. Descriptions of the WebLogic security providers are available under WebLogic Security Providers in Understanding Security for Oracle WebLogic Server and in later sections of this guide under the Do You Need to Create a Custom Provider_Type Provider? headings.

2. Determine which type of custom security provider you want to create.

The type may be Authentication, Identity Assertion, Principal Validation, Authorization, Adjudication, Role Mapping, Auditing, Credential Mapping, Versionable Application, or CertPath, as described in Types of Security Providers in Understanding Security for Oracle WebLogic Server. Your custom security provider can augment or replace the WebLogic security providers that are already supplied with WebLogic Server.

3. Identify which security service provider interfaces SSPIs you must implement to

create the runtime classes for your custom security provider, based on the type of security provider you want to create. The SSPIs for the different security provider types are described in Section 3.2, Security Services Provider Interfaces SSPIs and summarized in Section 3.2.6, SSPI Quick Reference.

4. Decide whether you will implement the SSPIs in one or two runtime classes.

These options are discussed in Section 3.2.5, Understand the SSPI Hierarchy and Determine Whether You Will Create One or Two Runtime Classes.

5. Identify which required SSPI MBeans you must extend to generate an MBean type

through which your custom security provider can be managed. If you want to provide additional management functionality for your custom security provider such as handling of users, groups, security roles, and security policies, you also need to identify which optional SSPI MBeans to implement. The SSPI MBeans are described in Section 3.3, Security Service Provider Interface SSPI MBeans and summarized in Section 3.3.6, SSPI MBean Quick Reference. 6. Determine how you will initialize the database that your custom security provider requires. You can have your custom security provider create a simple database, or configure your custom security provider to use an existing, fully-populated database. These two database initialization options are explained in Section 3.7, Initialization of the Security Provider Database. 7. Identify any database seeding that your custom security provider will need to do as part of its interaction with security policies on WebLogic resources. This seeding may involve creating default groups, security roles, or security policies. For more information, see Section 3.6, Security Providers and WebLogic Resources. Introduction to Developing Security Providers for WebLogic Server 2-3

2.2.2 Creating Runtime Classes for the Custom Security Provider by Implementing SSPIs