Before you begin
This subtask is part of the main task for creating a new scoped security role. Start with the main task: Create scoped security roles
Note: If you loaded security roles for the Web application from deployment descriptors using the Deployment Assistant, you need to Activate Changes and start the application in order to access the roles.
A scoped role for a Web Application resource applies either to the entire Web application and its contents or to individual resources contained in the Web application, such as JSPs and JARs.
The way you access scoped roles differs slightly depending on how your Web application is deployed. Start with step1 or step 2:
Deployments > MyEAR > Modules > MyWebAppModule
Deployments > MyWebAppModule
To apply a security role to the entire Web application and its contents: select Security > Application Scope > Roles and return to the main task: Start at
Create scoped security roles: step 2To apply a security role to a resource within the application: select Security > URL Patterns > Roles to display the URL Patterns and Roles page.
Caution: In WebLogic Server version 8.x the two
characters / * were used by the security container to indicate the
entire Web application contents. Starting with the current version,
BEA recommends that you use the / character, as it is the standard
J2EE syntax used by the Servlet container. If you want to continue
using /* you need to disable the
EnforceStrictURLPattern
field. For more
information, see Reset the
EnforceStrictURLPattern flag
![]() ![]() |