BEA WebLogic Server 7 사용자 설명서

BEA WebLogic Server 7.0 Upgrade Guide

f. Click the Membership tab to add the user who can boot WebLogic Server to the 

Administrators

 group.

g. Click the Apply button to save your changes.

5. Add the users and groups that you had configured in the 6.x security realm to an 

Authentication provider.

6. Optionally, define roles for your 6.x users and groups. See 

.

7. Express 6.x ACLs as security policies. See 

8. Set myrealm as the default security realm. See 

 

in Managing WebLogic Security.

9. Reboot WebLogic Server.

Each time WebLogic Server is booted and the server is deployed, the roles and 
security policies are applied. Subsequent access to the server and its methods are 
constrained by these roles and security policies until they are changed.

The scope of security realms changed in WebLogic Server 7.0. In WebLogic Server 
6.x, security realms provided authentication and authorization services. You chose 
from the File realm or a set of alternative security realms including the Lightweight  
Data Access Protocol (LDAP), Windows NT, UNIX or RDBMS realms. In addition, 
you could write a custom security realm.

In WebLogic Server 7.0, security realms act as a scoping mechanism. Each realm 
consists of a set of configured security providers, users, groups, roles, and security 
policies. Authentication and Authorization providers within a security realm offer 
authentication and authorization services.

You have the following choices when upgrading a 6.x security realm to WebLogic 
Server 7.0:

„

Use Compatibility security to access the users, groups, and ACLs configured in 
an LDAP, Windows NT, UNIX, RDBMS, or custom security realm. The Realm 
Adapter Authentication provider in the Compatibility realm can access users, 
groups, and ACLs stored in a 6.x security realm.