The current behavior of reading in config variables was not working as intended.
Rauthy reads the rauthy.cfg as a file first and the environment variables afterward. This makes it possible to
configure it in any way you like and even mix and match.
However, the idea was that any existing variables in the environment should overwrite config variables and therefore
have the higher priority. This was exactly the other way around up until v0.24.1 and has been fixed now.
How Rauthy parses config variables now correctly:
read rauthy.cfg
read env var
all existing env vars will overwrite existing vars from rauthy.cfg and therefore have the higher priority
The current behavior of reading in config variables was not working as intended.
Rauthy reads the
rauthy.cfg
as a file first and the environment variables afterward. This makes it possible to configure it in any way you like and even mix and match.However, the idea was that any existing variables in the environment should overwrite config variables and therefore have the higher priority. This was exactly the other way around up until
v0.24.1
and has been fixed now.How Rauthy parses config variables now correctly:
rauthy.cfg
rauthy.cfg
and therefore have the higher priority