Ok, that’s super strange. Normally, our server gives you a proper client_id using your FOREST_ENV_SECRET. Then it uses this client_id to perform the OIDC challenge.
- I’m not able to understand why the client_id is undefined in your case. Do you have FOREST_CLIENT_ID defined too? It should also be removed too.
I will try to see what can cause the issue on my side.
- In the meanwhile could you send me in PM the response from your http://localhost:3310/forest/authentication endpoint?
You should have anauthorizationUrl
in response (this URL is built into the agent using after calling our server to retrieve the client_id).
Really sorry for the inconvenience.
Kind regards,
Morgan