It includes attributes common to all security providers.
Every security provider must implement an MBean that
extends this MBean.

If the security provider supports management methods, the management
methods cannot be called until the validate method of realm in which
the security provider is configured successfully returns. That is,
the administrator must completely configure the realm before
using the management methods (for example, adding a user).

Deprecation of MBeanHome and
Type-Safe Interfaces

In addition to being used as
a base class that provides functionality to security provider
MBeans, JMX applications can use this class directly as a type-safe
interface. When used as a type-safe interface, a JMX application
imports this class and accesses it through
weblogic.management.MBeanHome. As of 9.0, the
MBeanHome interface and all type-safe interfaces for
WebLogic Server MBeans are deprecated. Instead, JMX applications that
interact with WebLogic Server MBeans should use standard JMX design
patterns in which clients use the
javax.management.MBeanServerConnection interface to
discover MBeans, attributes, and attribute types at runtime.

getDescription

Each security provider's MBean should set the default value
of this read-only attribute to a string that describes the
provider. In other words, each security provider's MBean
hard-wires its description. There are no conventions
governing the contents of the description. It should be a human
readable string that gives a brief description of the security provider.

getVersion

Each security provider's MBean should set the default value
of this read-only attribute to a string that specifies the version
of the provider (e.g. 7.3.04). In other words, each
security provider's MBean hard-wires its version. There
are no conventions governing the contents of the version string.