Issue running Asset Compute Service with OAuth Server-to-Server Auth – Missing Private Key Error | Community
Skip to main content
Basavaraj_K
Level 2
April 19, 2025
Question

Issue running Asset Compute Service with OAuth Server-to-Server Auth – Missing Private Key Error

  • April 19, 2025
  • 2 replies
  • 549 views

Hi everyone,

Has anyone successfully created an Asset Compute Service using OAuth Server-to-Server authentication?

I'm trying to get it running, but I hit an error when executing aio app run. It seems related to the private key, which is usually expected in JWT-based authentication, but not sure how that fits with the server-to-server OAuth setup.

Here's the error I'm seeing:
/test/tst-assets-customrendition-worker/node_modules/@adobe/asset-compute-devtool/client-build
⠦ Error: Missing Adobe Developer Project private key file.
(node:37759) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
TypeError: Cannot read properties of undefined (reading 'on')
Error: Command failed with exit code 1: adobe-asset-compute asset-compute:devtool
at makeError (/opt/homebrew/lib/node_modules/@adobe/aio-cli/node_modules/execa/lib/error.js:60:11)
at handlePromise (/opt/homebrew/lib/node_modules/@adobe/aio-cli/node_modules/execa/index.js:118:26)
at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
at async Run.runOneExtensionPoint (/opt/homebrew/lib/node_modules/@adobe/aio-cli/node_modules/@adobe/aio-cli-plugin-app/src/commands/app/run.js:125:7)
at async Run.run (/opt/homebrew/lib/node_modules/@adobe/aio-cli/node_modules/@adobe/aio-cli-plugin-app/src/commands/app/run.js:61:7)
at async Run._run (/opt/homebrew/lib/node_modules/@adobe/aio-cli/node_modules/@oclif/core/lib/command.js:117:22)
at async Config.runCommand (/opt/homebrew/lib/node_modules/@adobe/aio-cli/node_modules/@oclif/core/lib/config/config.js:329:25)
at async run (/opt/homebrew/lib/node_modules/@adobe/aio-cli/node_modules/@oclif/core/lib/main.js:89:16)
at async AIOCommand.run (/opt/homebrew/lib/node_modules/@adobe/aio-cli/src/index.js:38:12) {
shortMessage: 'Command failed with exit code 1: adobe-asset-compute asset-compute:devtool',
command: 'adobe-asset-compute asset-compute:devtool',
escapedCommand: 'adobe-asset-compute "asset-compute:devtool"',
exitCode: 1,
signal: undefined,
signalDescription: undefined,
stdout: undefined,
stderr: undefined,
failed: true,
timedOut: false,
isCanceled: false,
killed: false
}
press CTRL+C to terminate dev environment

 

It looks like it's still expecting a private key file, which doesn't quite align with how OAuth Server-to-Server tokens work. Has anyone run into this or managed to get around it?

Appreciate any guidance or insights!

Thanks in advance.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

2 replies

May 16, 2025

im facing the same issue

 

kautuk_sahni
Community Manager
Community Manager
July 2, 2025

@basavaraj_k Just checking in — were you able to resolve your issue?
We’d love to hear how things worked out. Feel free to share it — your insights could really benefit the community. Thanks again for being part of the conversation!

Kautuk Sahni