adobe / reactor-downloader Goto Github PK

Running npm install fails with the following error:

npm ERR! code UNABLE_TO_GET_ISSUER_CERT_LOCALLY
npm ERR! errno UNABLE_T0_GET_ISSUER_CERT_LOCALLY
npm ERR! request to https: //artifactory.corp.adobe. com/artifactory/api/npm/npm-adobe-release/yargs-parser/-/yargs-parser-9.0.2.tgz failed, reason: unable to get local issuer certificate

It looks like this package tries to connect to an Adobe Internal server that I don't have access to.

I was hoping to use this package to produce the reactor-settings.json file that @adobe/reactor-sync requires.

I was trying to pull down an instance and kept returning this error:
Error: Error retrieving access token. The metascopes in the JWT are not a subset of the metascopes in the binding.

Maybe someone should take a look at it? I was able to correct by inserting a hard path, see code block
try { // getAccessToken args.accessToken = await getAccessToken({ environment: args.environment, integration: { clientId: args.apiKey, clientSecret: args.clientSecret, privateKey: args.privateKey, payload: { iss: args.orgId, sub: args.techAccountId, aud: args.environment.aud + args.apiKey, // METASCOPE FIX --> line 190 'https://ims-na1.adobelogin.com/s/ent_reactor_sdk': true } } });

On Windows 10 generally symlinks are restricted to elevated privilege so if a user is not elevated the downloader will fail. Is is possible to add a change to this tool to gracefully handle this condition? Propose that if symlinks are not allowed the downloader can still proceed without creation of human readable symlinks and warn user of this.

Right now all the docs and source code seem to suggest that JWT is the only method for authentication. What is the plan for allowing Oauth Server to Server which we are going to need to use after this year?

Hi @bbythewa,

Thank you so much for building this tool. I absolutely love it. It's helped my workflow tremendously. I'm sad that it doesn't appear to be actively maintained anymore.

I have my own fork, but is there any way you would allow someone from outside Adobe to maintain this project so it remains useful for the community? If so I'd love to volunteer!

Some things I'd love to see/help make happen:

• Upgrading auth from JWT to OAuth S2S
• Removing internal Adobe artifactory dependency
• Other QOL improvements

Please let me know!