Setting the WSIdentityPermission

The Web service client (for example, the SOA reference binding component) where you attached the wss11_saml_token_identity_switch_with_message_protection_client_policy must have the oracle.wsm.security.WSIdentityPermission.

To use Fusion Middleware Control and add the oracle.wsm.security.WSIdentityPermission to the SOA reference binding component as a System Grant, perform the following steps:

  1. In the Navigator pane, expand WebLogic Domain to show the domain where you need to configure the application. Select the domain.
  2. Using Fusion Middleware Control, click WebLogic Domain, Security, System Policies. System policies are the system-wide policies applied to all applications deployed to the current WebLogic Domain.
  3. From the System Policies page, select the arrow icon in the Permission field to search the system security grants.
  4. Select one of the codebase permissions to use as a starting point and click Create Like.
  5. In the Grant Details section of the page, enter file:${common.components.home}/modules/oracle.wsm.agent.common_11.1.1/wsm-agent-core.jar in the Codebase field.
  6. In the Permissions section of the page, select the starting point permission class and click Edit.
  7. In the Permission Class field, enter oracle.wsm.security.WSIdentityPermission. The resource name is the composite name for SOA and the application name for a J2EE client. The action is always assert.

Related Topics

Configuring SAML Web Service Clients for Identity Switching without Message Protection

Message Protection Policy

Creating the basic.credentials Key

Applying the New Policy

Configuring a Keystore if One Is Not Configured



Legal Notices | Your Privacy Rights
Copyright © 1999, 2023

Last Published Thursday, January 12, 2023