Executive Summary
The Lenzing Pro Product Catalog page currently returns a 500 error when product data should be loaded from SAP Commerce Cloud. MTNA testing indicates that the issue is not caused by the frontend, Droplet or .env configuration. The most likely cause is a defective SAP CC OAuthClientDetails record for trusted_client in the d1/dev environment.
Technical Summary
MTNA tested several OAuth and OCC scenarios. The configured backend client trusted_client returns the error “redirectUris cannot be empty”. The same error appears when using the standard OOTB trusted_client credentials and even when using trusted_client with an intentionally wrong secret. A bogus client returns the expected client_id authentication error, which indicates that the auth server is reachable and distinguishes clients correctly. An anonymous OCC endpoint returns HTTP 200, confirming that SAP Commerce Cloud itself is reachable. This strongly suggests that the trusted_client record exists but is internally misconfigured, most likely because redirectUris is empty.
Client Summary
Our tests indicate that the current 500 error is most likely caused by the SAP Commerce Cloud d1/dev OAuth client configuration, not by MTNA frontend, backend, Droplet or environment configuration. The trusted_client record appears to be present but incomplete, and SAP CC fails with “redirectUris cannot be empty”. We recommend that Lenzing / IBM / the responsible SAP CC team checks whether the trusted_client OAuthClientDetails record was changed or reset during a recent deployment, rebuild, re-initialization or ImpEx import.
Proposed Fix
On SAP CC d1/dev side, set a non-empty redirectUris value for trusted_client, for example via ImpEx:
INSERT_UPDATE OAuthClientDetails;clientId[unique=true];redirectUris
;trusted_client;https://api.mtna-lp.dev/callback
Although MTNA uses the client_credentials grant and does not functionally rely on a redirect URI, SAP Commerce Cloud appears to require this field to be non-empty during OAuth client validation.
Next Action
Replace the placeholder verification with the real Product Catalogue retest result and confirm the OAuth grant type and Nuxt.js implementation impact.
Retest Result
SIMULATED PLACEHOLDER DATA — NOT A REAL TECHNICAL TEST RESULT
PLACEHOLDER FLOW TEST — NOT A REAL TECHNICAL RESULT
The simulated workflow assumes that the previous redirectUris validation error was no longer reproduced after IBM's configuration update.
The actual Product Catalogue result, OAuth grant type and Nuxt.js implementation impact remain unverified.
A real developer retest is still required.
Impact Review Notes
SIMULATED PLACEHOLDER DATA — NOT A REAL TECHNICAL TEST RESULT
Placeholder assessment only.
The real impact review must determine:
• whether a Nuxt.js authentication change is required,
• whether additional testing or deployment work is needed,
• whether the effort is within the current scope,
• whether a Change Request or new PO is required,
• and which governance process should be introduced for future IBM/SAP upgrades.
Governance & Communication
Human ReviewRequired
Portal Publish StatusIn Review
Client CommunicationSent
Communication DateJul 09, 2026
Communication ChannelEmail
Closure ReasonNot closed
Operating OSClient Portal