The engine inject the env MESG_TOKEN that is currently simply the instance's hash but should be updated to a real auth system.
The problem is the instance need to know its hash to use the API execution and event.
My suggestion is to introduce a new env MESG_INSTANCE_HASH that contains the instance hash for ever and use it instead of MESG_TOKEN.
We can keep MESG_TOKEN as it currently is to not break current service and update its functionality when we implement the auth system.
NicolasMahe
commented
4 years ago
The engine inject the env
MESG_TOKENthat is currently simply the instance's hash but should be updated to a real auth system. The problem is the instance need to know its hash to use the API execution and event. My suggestion is to introduce a new envMESG_INSTANCE_HASHthat contains the instance hash for ever and use it instead ofMESG_TOKEN. We can keepMESG_TOKENas it currently is to not break current service and update its functionality when we implement the auth system.