Using environment variables in properties in 4.1

Wessel, Keith kwessel at illinois.edu
Fri May 21 15:41:01 UTC 2021


Hi, all,

I was using the following syntax to pull in properties in 4.0 in my containerized IdP.

idp.duo.integrationKey = ${DUO_INTEGRATION_KEY}

DUO_INTEGRATION_KEY, in this case, was a system environment variable that Docker was setting at boot time. The IdP, not finding a property by the name of DUO_INTEGRATION_KEY, was using the system environment where it then pulled in the env var by that name.

In my upgrade to 4.1, this is no longer working. The Duo class throws an exception saying that the integration key isn't valid, but when I put the literal value in that property, it works.

Did something change between 4.0 and 4.1 regarding the ability to reference system environment variables in property files? More importantly, is there a more proper (and still functioning) way to do this?

Thanks,
Keith



More information about the users mailing list