Security Realms Administration Portlet
Portlet Title | Security Realms Administration |
Portlet Name | wm_securityreamadmin |
Portlet File Name | wm_securityreamadmin.pdp |
Top-level Folder | admin |
JSR168 Portlet? | No |
Alias | /portlet/wm_securityrealmadmin |
Default Instances of the portlet | Folders > Administrative Folders > Administration Dashboard > Configuration > Security Realms Administration |
Security. Administrators use this portlet to define security realms. Use security realms to simplify permissions management. By default, administrators define permissions for each resource in My webMethods Server. Instead, using this portlet, administrators can define security realms, assign resources to the security realms, and then set permissions for the security realms. As a result, rather than individual permissions per resource, permissions are against a collection of resources in a security realm.
From this portlet, an administrator can:
Create security realms.
Delete security realms.
Manage permissions assigned to security realms.
Manage the
My webMethods Server resources that are assigned to each security realm.
Administrators can organize the security realms by grouping them into folders, called containers.
Optionally, an administrator can configure the security realm to delegate permission decisions to an external security provider.
To configure the security realm to delegate permission decisions to an external security provider, do the following:
1. Click the name of a Security Realm container, for example, Portal Resources.
2. On the Tools menu of the security realm you want to modify (for example, the Administrative Commands security realm), select Modify Security Realm.
3. For the Extended Type field, click Browse.
4. Select the security provider you want to use (for example, if you installed the HTTP Header Policy security provider, select form > wm_xt_httpheaderpolicy).
5. Click Update.
When you link the security realm to an external security provider, permissions set on the security realm itself are no longer relevant; all permission decisions are delegated to the security provider.
