Can env vars be referenced in shibboleth2.xml?

[Wessel, Keith]

Well, until I relized it was placed in its own directly (notably /run/shibboleth) I thought it might be in a directory with other sockets, and I didn't know if I wanted to share all of that. Of course, Scott's symlink trick would work around that, too. But since it's in /run/shibboleth, I should just be able to make that a non-persistent shared volume between my containers. So, you're correct; I don't need to change its location.

Keith


-----Original Message-----
From: users <users-bounces at shibboleth.net> On Behalf Of Peter Schober
Sent: Wednesday, September 30, 2020 10:12 AM
To: users at shibboleth.net
Subject: Re: Can env vars be referenced in shibboleth2.xml?

* Wessel, Keith <kwessel at illinois.edu> [2020-09-30 16:41]:
> Scott, any chance that there's an undocumented env var for the 
> location of the Unix socket that both shibd and mod_shib will consult? 
> If not, I can just include a modified shibboleth2.xml in both 
> containers, but an env var would be lovely.

Why would you need to make the Unix domain socket's location dynamic, too?
Just share/mount where it currently is?

-peter
--
For Consortium Member technical support, see https://wiki.shibboleth.net/confluence/x/coFAAg
To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net