On Tue, Nov 29, 2016 at 2:18 PM, Lance LeFlore <lance at 3t218.org> wrote:
> Hi There,
>
> I would like to begin discussion around a new config-per-{user,group} option.
>
> This new configuration option, let's call it: custom-env (exported as,
> say, OCSERV_CUSTOM_ENV), would act purely as an variable to be
> exported during execution of connect/disconnect-script. It would not
> be consumed by Ocserv in any (other) way.
> My use case is that I would like to store a small bit of metadata in
> config-per-user which is then exported and used to inform the URL to a
> REST API Ocserv is calling upon client connect and disconnect.
Makes sense to have something like that. Could that be something that
can be used by radius as well? I wouldn't like the file and radius
config backends to deviate much.
regards,
Nikos
