Issue with Passing OIDC Access Token to OpenText xECM REST API
Hi all,
I'm developing a REST API that interacts with the OpenText xECM REST API. My API receives requests from another application where users are authenticated using OIDC (with Entra ID as the issuer). The requests include a JWT access token in the Authorization header.
My goal is to pass this token (after validation or necessary processing) to the xECM REST API so that all requests are made within the context of the authenticated user.
Here's the setup:
- In OTDS, I have an OpenID authentication handler connected to Entra ID, which works fine for UI logins.
- I’ve also explored exchanging a base64-encoded ID_TOKEN for an OTDS ticket using the
/otdsws/rest/authentication/token
endpoint, which works, but requires an additional authentication handler due to field differences.
However, when I attempt to pass the access token directly as a bearer token to the xECM REST API (without an OTDS or OTCS ticket), xECM seems to recognize it as an OAuth token and forwards it to OTDS for validation, but I always get "Access Denied" or "Invalid OAuth object" in OTDS.
Has anyone implemented a similar flow where an OAuth/OIDC access token is passed directly to the xECM REST API? Is this supported, and if so, what might I be missing? I haven't been able to find clear documentation on this.
Any insights would be appreciated!
Categories
- All Categories
- 123 Developer Announcements
- 54 Articles
- 150 General Questions
- 148 Thrust Services
- 57 OpenText Hackathon
- 37 Developer Tools
- 20.6K Analytics
- 4.2K AppWorks
- 9K Extended ECM
- 918 Core Messaging
- 84 Digital Asset Management
- 9.4K Documentum
- 32 eDOCS
- 186 Exstream
- 39.8K TeamSite
- 1.7K Web Experience Management
- 8 XM Fax
- Follow Categories