Get rendering id of current env

[Thong_Dang]

Feature(s) impacted

Hi, I need somehow to obtain the rendering id of current env (set by FOREST_ENV_SECRET), which I believe can be call by some rest API.

As I can see in the client library, we can have get request to https://api.forestadmin.com/liana/{some-path} with forest-secret-key as header.

The problem is these API endpoint is not documented anywhere.

Could you guys please help?.

This rendering id is very important because I want to use this feature:

const recordGetter = new RecordsGetter(NewPaymentModel, { renderingId: forestEnvId } as User, ctx.query);

Observed behavior

Expected behavior

Failure Logs

Context

• Project name: …
• Team name: …
• Environment name: …
• Agent (forest package) name & version: “forest-express-mongoose”: “^9.3.2”
• Database type: …
• Recent changes made on your end if any: …

[morganperre]

Hello @Thong_Dang,

@Thong_Dang

The problem is these API endpoint is not documented anywhere.

Indeed, this is intentional. The logic is hidden within your forest-express-mongoose agent.

As I answered in the last topic you should have the request.user automatically setted by the authentication middleware (which avoid doing some fancy stuff).

Export of forest-express-mongoose QueryBuilder

Hello @Thong_Dang, Great that it works but it’s pretty weird that the user (request.user) is undefined. You are probably missing the ensureAuthenticated middleware on this route which is also weird. Example of globally mounted ensureAuthenticatedmiddleware const { ensureAuthenticated, PUBLIC_ROUTES, } = require('forest-express-mongoose'); ... app.use('/forest', (request, response, next) => { if (PUBLIC_ROUTES.includes(request.url)) { return next(); } return ensureAuthenticate…

• The question is Do you have the ensureAuthenticated middleware mounted on your project?

• Could you share your project name ?

• How did you integrate forest-express-mongoose within your app?

Thanks for your anwsers.

Kind regards,
Morgan

[Thong_Dang]

@morganperre

you shoul

Hi, thanks for your response, really appreciated.

We don’t use express as server library but we are using koa, and their middleware are not compatible, hence the issue with authorization header parsing.

I managed to fix this by an simple ctx.req.headers assignment.

Thanks again!

[morganperre]

Hey @Thong_Dang,

@Thong_Dang

I managed to fix this by an simple ctx.req.headers assignment.

Nice that you found out.

@Thong_Dang

We don’t use express as server library but we are using koa, and their middleware are not compatible, hence the issue with authorization header parsing.

Our new agent Node.js is natively compatible with Koa.
It might be the right path for you in the future as the developer experience is highly improved and it comes with new features.

Kind regards,
Morgan