E-IB: User ID Requirements and Minimal Permissions for Integration Broker Setup and Messaging (Doc ID 785863.1)

Last updated on APRIL 25, 2016

Applies to:

PeopleSoft Enterprise PT PeopleTools - Version 8.40 and later
Information in this document applies to any platform.

This document was previously published on Oracle PeopleSoft Customer Connection website as:
Solution 201055255: E-IB/SEC: Minimal userid perms to run IB messaging

*** Latest revision: 25-Apr-2016 ***

Goal

Integration Broker to successfully perform its tasks in running application messaging uses certain User IDs in its setup.

The primary question is:

What are the requirements or minimal permissions that a User ID must have to be used in Integration Broker setup?

    The User ID above, depending on usage scenario and PeopleTools release version, may refer any of:

  1. User ID in a PeopleSoft integration gateway properties for a PeopleSoft node Jolt connection
  2. User ID that runs the receiving application server domain (be it local or remote)
  3. User ID that runs the PeopleSoft user session in which the application messaging service operations are initiated
  4. User ID specified in the URL, HTTP parameters or UserToken tags of a SOAP header of an incoming message
  5. Default User ID of the sending (source, "From") node (when the sending specifies such node, but no explicit User ID)
  6. Default User ID of the ANONYMOUS node (when neither a valid sending node applies nor an explicit User ID is specified)

An additional corollary question is:

Can a User ID that is used in the Integration Broker related setup be exempt from password expiration?

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms