Technical data

Defining Users
Administration Guide 14-39
n If you are using a custom security realm, follow the steps in “Installing a
Custom Security Realm” to specify information about how the Users, Groups,
and optionally ACLs are stored in your custom security realm.
n The Delegating security realm is no longer supported. If you are using the
Delegating security realm, you will have to use another type of security realm to
store Users, Groups, and ACLs.
n If you are using the RDBMS security realm, use one of the following options to
convert the security realm:
l If you did not change the source for the RDBMS security realm, follow the
steps in “Configuring the RDBMS Security Realm” to instantiate a new class
for your existing RDBMS security realm and define information about the
JDBC driver being used to connect to the database and the schema used by
the security realm. In this case, you are creating a MBean in WebLogic
Server for the RDBMS security realm.
l If you customized the RDBMS security realm, convert your source to use the
MBeans. Use the code example in the
\samples\examples\security\rdbmsrealm directory as a guide to
converting your RDBMS security realm. Once you have converted your
RDBMS security realm to MBeans, follow the instructions in“Configuring
the RDBMS Security Realm” to define information about the JDBC driver
being used to connect to the database and the schema used by the security
realm.
Defining Users
Note: This section explains how to add Users to the File realm. If you are using an
alternate security realm, you must use the administration tools provided in that
realm to define a User.
User and group names must be unique. You can use multibyte characters and
all special characters except a comma (
,) in user and group names.