How to Pass Authorization Data for authInternalUsers via Environment Variables in Mediamtx?

[timerlan]

Question

Hi everyone,

I'm using Mediamtx for my media streaming project, and I need to configure the authInternalUsers parameter to manage user authentication. I want to store the user credentials securely in an .env file and pass them to the configuration.

Could someone provide guidance on how to achieve this?

Here are the different ways I've tried to set the environment variables, but none of them seem to work:

1. As a JSON string:

MTX_AUTHINTERNALUSERS={"authInternalUsers":[{"user":"any","pass":null,"ips":["127.0.0.1","::1"],"permissions":[{"action":"publish"},{"action":"api"},{"action":"metrics"},{"action":"pprof"}]},{"user":"test","pass":"test","ips":[],"permissions":[{"action":"read"}]}]}

2. Using individual environment variables for each property:

MTX_AUTHINTERNALUSERS_0_USER=any
MTX_AUTHINTERNALUSERS_0_PASS=""
MTX_AUTHINTERNALUSERS_0_IPS_0='127.0.0.1'
MTX_AUTHINTERNALUSERS_0_IPS_1='::1'
MTX_AUTHINTERNALUSERS_0_PERMISSIONS_0_ACTION=publish
MTX_AUTHINTERNALUSERS_0_PERMISSIONS_1_ACTION=api
MTX_AUTHINTERNALUSERS_1_USER=test
MTX_AUTHINTERNALUSERS_1_PASS=test
MTX_AUTHINTERNALUSERS_1_IPS="[]"
MTX_AUTHINTERNALUSERS_1_PERMISSIONS_0_ACTION=read

3. Using an alternative notation for array indices:

MTX_AUTHINTERNALUSERS_[0]_USER=any
MTX_AUTHINTERNALUSERS_[0]_PASS=""
MTX_AUTHINTERNALUSERS_[0]_IPS_[0]='127.0.0.1'
MTX_AUTHINTERNALUSERS_[0]_IPS_[1]='::1'
MTX_AUTHINTERNALUSERS_[0]_PERMISSIONS_[0]_ACTION=publish
MTX_AUTHINTERNALUSERS_[0]_PERMISSIONS_[1]_ACTION=api
MTX_AUTHINTERNALUSERS_[1]_USER=test
MTX_AUTHINTERNALUSERS_[1]_PASS=test
MTX_AUTHINTERNALUSERS_[1]_IPS="[]"
MTX_AUTHINTERNALUSERS_[1]_PERMISSIONS_[0]_ACTION=read

None of these approaches seem to be working. How can I properly pass and parse these credentials from the environment variables into the Mediamtx configuration?

Any guidance or examples would be greatly appreciated!

Thanks in advance for your help!

[timerlan]

#3378

[bluenviron-bot]

This discussion is being locked automatically because the last update was more than 2 years ago.

Do not use the content of this discussion as reference since it's probably outdated!

The official documentation is the only place in which you can find up-to-date answers.