Security - Oracle WebLogic Server 12c Advanced Administration - page 249

username=wlsadmin
password=wlspwd123
3. Start the Administration Server.
How it works...
The first step created the tables in the database to store the user and group data.
It is necessary to insert the provided groups into the new provider to
maintain consistency with the default global roles in the WebLogic Server.
We created the provider PRODSQLProvider with the default values, including the use of
encrypted passwords only. We created the data source ds-Provider and associated it with
the provider to handle the database connection.
We changed the order of the providers such that PRODSQLProvider is placed before the
DefaultAuthenticator provider. With both providers configured with the SUFFICIENT
control flag, WebLogic will try to authenticate first on PRODSQLProvider ; if authentication
fails, it will try on DefaultAuthenticator . A possible alternative configuration is to delete
DefaultAuthenticator and leave only PRODSQLProvider with the REQUIRED control flag.
It's an option to leave DefaultAuthenticator as a
second provider in case of a database outage.
We also changed the boot.properties file to match a username and password from the
new database authentication provider.
See also
F Securing a web application with basic authentication
Assigning a user to a group
In this recipe, a new group called myAuthGroup will be created and a new user, authUser ,
will be created and assigned to this group. PRODSQLProvider will be used.