Account type: Sandbox (XXXXX-sb1)
We're implementing OAuth 2.0 Client Credentials (Machine to Machine) for a RESTlet integration, following SuiteAnswers Articles 24807, 101101/101102, and 101109 exactly. Every POST to the token endpoint returns:
HTTP 500 Internal Server Error
{"error":"server_error"}
Confirmed correct per documentation:
- JWT header:
typ=JWT, alg=PS256, kid=<Certificate ID> - JWT payload: exactly
iss, scope (array), aud (token endpoint URL), iat, exp — nothing extra - Certificate: RSA 4096-bit, uploaded/mapped successfully via OAuth 2.0 Client Credentials (M2M) Setup
- Signature independently self-verified as valid before every send
- Private key confirmed matching the uploaded certificate (modulus comparison)
- Tested against both a scoped custom role and Administrator — identical failure
- Tested via two independent implementations (PowerShell/.NET and Python/PyJWT) — identical failure
Per Article 102607, server_error isn't even a documented response for this endpoint (only invalid_request/400 and invalid_token/401 are listed) — suggesting an unhandled server-side exception rather than a validated rejection.
Login Audit Trail shows blank-identity Failure entries at matching timestamps, but no detail beyond that, and no evidence the request ever reaches full authentication evaluation.
We have an open Oracle support case (#7109272) currently under review by the SuiteBuilder/SuiteScript team. Has anyone else hit this exact failure on Client Credentials M2M? Any known account-level gotchas not covered in the standard setup docs?