Understanding Request Authentication for Installation about request.js

[gr2m]

The 404 error is see is not coming from the GET /app/orgs/:org/projects request, but from POST https://api.github.com/app/installations//access_tokens. The createAppAuth strategy is sending the request to retrieve an installation token automatically for you, you don't need to do that manually.

What you need to do though is to set the auth.installationId option.

Try this

new Octokit({
  authStrategy: createAppAuth,
  auth: {
    id: process.env.GITHUB_APP_ID,
    privateKey: pemKey,
    installationid
  },
  userAgent: "blabla",
  previews: ["inertia"],
});

await session.request("GET /app/orgs/:org/projects", {
  headers: {
    authorization: `token ${installToken}`,
  },
  org,
});

[PierFio]

Thanks a lot for the fast help and this whole framework. That way, it works. Surprisingly (I was looking at that), this is not working though:

const sessionMaker = Octokit.defaults({
     authStrategy: createAppAuth,
      auth: {
          id: process.env.GITHUB_APP_ID,
          privateKey: pemKey,
      },
      userAgent: 'blabla',
      baseUrl: 'https://api.github.com',
      previews: ['inertia', 'machine-man'],
});

followed by

const session = new sessionMaker(options =>  
    ({
         ...options,
         auth: {
            ...options.auth,
            installationId,
            permissions: {
                organization_projects: 'write',
            }
         },
    })
);

[gr2m]

you are passing a function to sessionMaker, try passing the options object instead

const session = new sessionMaker({
  ...options,
  auth: {
    ...options.auth,
    installationId,
    permissions: {
      organization_projects: "write",
    },
  },
});

[PierFio]

Yes, thank you, you are right of course. But do not you think that defeats the purpose of the default options? I mean I have defined a defaultOptions object that I specialize when calling a specific new Octokit(). But certainly not a big deal anyway...

[gr2m]

You can create a constructor which has the app auth strategy and app ID + private key configured

const OctokitWithAppAuth = Octokit.defaults({
  authStrategy: createAppAuth,
  auth: {
    id: process.env.GITHUB_APP_ID,
    privateKey: pemKey,
  },
});

Then use that custom constructor to initiate instances for an installation

const octokit = new OctokitWithAppAuth({
  auth: {
    installationId
  },
});

[PierFio]

Neat and nice. Thank you Gregor.