I will migrate oracle fusion and oic integrations from basic auth to oauth2


About this gig
- Oracle is ending password (basic) authentication for Fusion Cloud REST and SOAP services on 31 March 2027. Every integration that calls Fusion with a username and password (OIC connections, middleware, scripts, third-party apps) has to move to token-based auth.
I'm an Oracle Integration (OIC/OCI) architect with 13 years in IT. I'll do this migration with you, written and async:
- Inventory: which integrations still use basic auth, and which endpoints (REST, SOAP, ESS, BI Publisher) need extra care
- OAuth 2.0 confidential app setup in the OCI IAM identity domain, client credentials or user-assertion grant, certificate and scope steps
- OIC connection changes (Fusion/ERP Cloud adapter, REST adapter) and token calls for scripts or Postman
- Test plan and runbook for DEV -> TEST -> PROD
You keep full control: I write the exact steps and review your screenshots and logs, or work in your instance if you give a test login. No production passwords are needed.
Message me with how many integrations you have and I'll confirm the right package.
Get to know Rahul S
Web Scraping, Apify and AI Automation Engineer
- FromIndia
- Member sinceOct 2026
Languages
Hindi, English
FAQ
Is the deadline real?
Yes. Oracle announced it on Customer Connect, and the date given is 31 March 2027.
Do you need our passwords?
No. Screenshots and logs are enough for the plan. For hands-on work, use a test-instance user you can disable afterwards.
Do you need a call?
No. Everything is written, in Fiverr messages.
What about SOAP services like ESS or BI Publisher?
Some SOAP context roots are not on Oracle's token-auth list, so I check each one and propose a supported path (REST equivalents or adapter changes).
