Integration Technologies - JDE1 (MOSC)

MOSC Banner

oauth migration

in Integration Technologies - JDE1 (MOSC) Question

We use OIC Gen3 to invoke Fusion BI Publisher ScheduleService.scheduleReport. Our connection uses Security Policy = NONE, while the SOAP request contains userID and password mapped within OIC.Please confirm:

  1. Does the authentication deprecation affect username/password fields in SOAP request bodies?
  2. Does scheduleReport support OAuth 2.0 with JWT User Assertion and a Bearer token?
  3. Under OAuth, should userID and password be omitted, empty, or handled differently?
  4. Is the Publisher OAuth runtime property supported in our Fusion ERP/HCM environment?
  5. If not, which supported API or ESS approach replaces scheduleReport for scheduled CSV delivery?
  6. What is the exact enforcement date for our Fusion release?

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

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

Category Leaderboard

Top contributors this month

E1 Integrations Tags

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center