Creating Runtime Classes for the Custom Security Provider by Implementing SSPIs Generating an MBean Type to Configure and Manage the Custom Security Provider

Introduction to Developing Security Providers for WebLogic Server 2-3

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

In one or two runtime classes, implement the SSPIs you have identified by providing implementations for each of their methods. The methods should contain the specific algorithms for the security services offered by the custom security provider. The content of these methods describe how the service should behave. Procedures for this task are dependent on the type of security provider you want to create, and are provided under the Create Runtime Classes Using the Appropriate SSPIs heading in the sections that discuss each security provider in detail.

2.2.3 Generating an MBean Type to Configure and Manage the Custom Security Provider

Generating an MBean type includes the following steps: 1. Create an MBean Definition File MDF for the custom security provider that extends the required SSPI MBean, implements any optional SSPI MBeans, and adds any custom attributes and operations that will be required to configure and manage the custom security provider. Information about MDFs is available in Section 3.3.3, Understand the Basic Elements of an MBean Definition File MDF, and procedures for this task are provided under the Create an MBean Definition File MDF heading in the sections that discuss each security provider in detail. 2. Run the MDF through the WebLogic MBeanMaker to generate intermediate files including the MBean interface, MBean implementation, and MBean information files for the custom security providers MBean type. Information about the WebLogic MBeanMaker and how it uses the MDF to generate Java files is provided in Section 3.3.5, Understand What the WebLogic MBeanMaker Provides, and procedures for this task are provided under the Use the WebLogic MBeanMaker to Generate the MBean Type heading in the sections that discuss each security provider in detail. 3. Edit the MBean implementation file to supply content for any methods inherited from implementing optional SSPI MBeans, as well as content for the method stubs generated as a result of custom attributes and operations added to the MDF. 4. Run the modified intermediate files for the MBean type and the runtime classes for your custom security provider through the WebLogic MBeanMaker to generate a JAR file, called an MBean JAR File MJF. Procedures for this task are provided under the Use the WebLogic MBeanMaker to Create the MBean JAR File MJF heading in the sections that discuss each security provider in detail. 5. Install the MBean JAR File MJF into the WebLogic Server environment. Procedures for this task are provided under the Install the MBean Type into the WebLogic Server Environment heading in the sections that discuss each security provider in detail.

2.2.4 Writing Console Extensions