React-OpenText xECM Integration
Budget / SalaryHourly project
TypeFreelance project
LocationRemote
Posted2 hours ago
I need to wire my existing React front-end and Node/Express back-end (with a MS SQL data store) into our OpenText xECM environment. The goal is simple for the user but intricate under the hood: when someone clicks the “Upload” button in my app, an OpenText widget must appear, let them choose a target folder, and then store the file in xECM—always respecting the permissions enforced by OTDS.
Authentication and authorization
OTDS sits at the center of our security model. OAuth is my preferred protocol, yet I’m happy to discuss SAML or JWT if you have a convincing argument. Whatever we choose, the user must see only the repositories and folders they are already entitled to.
OpenText service layer
We’ll need to call both Content Web Services and the newer REST endpoints. I’m looking for clean, well-documented code examples that I can maintain, not black-box libraries.
Workflow in the UI
• A button click triggers the upload flow.
• The OpenText widget opens inside the React app to pick the destination folder.
• Once the user confirms, the file is uploaded, metadata saved, and a success message returned to the UI.
Deliverables
1. Secure OAuth (or mutually agreed alternative) flow against OTDS.
2. React component(s) that launch and manage the OpenText folder-picker widget.
3. Node/Express endpoints that bridge to both CWS and REST services for file create, metadata, and permission checks.
4. Clear setup instructions plus brief inline documentation so my team can extend the solution later.
5. A quick demo showing the entire click-to-commit sequence working end-to-end.
If you’ve integrated xECM before and can move quickly on this, let’s talk.
Authentication and authorization
OTDS sits at the center of our security model. OAuth is my preferred protocol, yet I’m happy to discuss SAML or JWT if you have a convincing argument. Whatever we choose, the user must see only the repositories and folders they are already entitled to.
OpenText service layer
We’ll need to call both Content Web Services and the newer REST endpoints. I’m looking for clean, well-documented code examples that I can maintain, not black-box libraries.
Workflow in the UI
• A button click triggers the upload flow.
• The OpenText widget opens inside the React app to pick the destination folder.
• Once the user confirms, the file is uploaded, metadata saved, and a success message returned to the UI.
Deliverables
1. Secure OAuth (or mutually agreed alternative) flow against OTDS.
2. React component(s) that launch and manage the OpenText folder-picker widget.
3. Node/Express endpoints that bridge to both CWS and REST services for file create, metadata, and permission checks.
4. Clear setup instructions plus brief inline documentation so my team can extend the solution later.
5. A quick demo showing the entire click-to-commit sequence working end-to-end.
If you’ve integrated xECM before and can move quickly on this, let’s talk.
Apply on Freelancer →
Project sourced from Freelancer.com. Applications happen directly on the original platform — we never collect your data.