SOA Users with Application Roles Require Special Permissions to Perform Operations in Secure Mode

Issue

Bug Number: 36841322

Impacted Releases: 14.1.2.0.0

Impacted Platforms: All

Users with application roles such as default_composer, SOAOperator, SOAMonitor, and so on, face the following error when performing operations in secure mode.

[test_log] [INFO] [exec] Connecting to
        t3s://phxpffag40.dev2farmphx3.screvenfar02phx.oraclevcn.com:9002 with userid
        partitioncomposeruser ...
      [test_log] [INFO] [exec] <Jul 10, 2024, 6:14:55â€¯AM Pacific Daylight Time> <Info>
          <Security> <BEA-090908> <Using the default WebLogic SSL Wildcard Hostname Verifier
          implementation.> 
      [test_log] [ERROR] [exec] This Exception occurred at Wed Jul 10 06:14:55 PDT
        2024.
      [test_log] [ERROR] [exec] java.lang.SecurityException: User partitioncomposeruser does
          not have access to the administrator port.

Workaround

When secure mode is enabled, all the admin traffic (including MBean Access) is directed to the admin channel. The admin channel is available only to users with an admin role. Thus, to perform operations in secure mode, users with application roles such as default_composer, SOAOperator, SOAMonitor, and so on, require access to AdminChannel. See Users, Groups, And Security Roles. Below are the list of roles and their corresponding access privilege to the admin channel.

Admin role : Read & Write Access
Monitor role : Read Access
App Tester role : Read Access