Setting internal attributes per client

[Alan DeKok]

On Oct 29, 2017, at 10:25 PM, Nathan Ward <lists+freeradius at daork.net> wrote:
> Looking at the code I didn’t find anything with “mygroup” or anything, and having a bit of a test, it looks like anything specified under a client section can be requested this way, whether it’s a permitted configuration or not. I can do:
> 
> client blah {
>  hello = “test”
> }
> 
> Then retrieve it with %{client:hello}.

  Yes.

> I presume this is by design? Can I use any arbitrary name here? (Of course, I’ll make it something specific to my installation, so there’s no conflict with future client parameters).
> The client Xlat looks very useful.

  It's by design.  The configuration files are a read-only key-value database.

> I don’t see this documented anywhere other than the Xlat code, and a couple of examples where it’s used but not explained. I tried to edit https://wiki.freeradius.org/config/Xlat <https://wiki.freeradius.org/config/Xlat> to add this, but it doesn’t seem to get access to my email address from the Github OAuth thing so I can’t get edit access. Can I contribute this somehow?

  I'll take a look.

  Alan DeKok.