Kostas Kalevras <[EMAIL PROTECTED]> wrote:
> Hmm, I don't think you can do what you want right now. Alan, what would you
> think about adding something like this in authenticate/authorize sections of
> radiusd.conf:
> 
> realmname isp1{
>       ldap1
> }

  Maybe.  We need a general way of controlling how and when each
module is called.  This would be some kind of meta configuration.

  I'm not sure how to do it in general, so I'm holding off on any
implementation.  And I *hate* specific solutions and patches.  They
make the code more complicated, without being terribly helpful.

  Off of the top of my head, it may be interesting to do:

authorize {
  ...
  if (%{request:Realm} == "isp1") {
                   ldap1
  }
  ...
}

  Then the module code can call xlat on the string, do a comparison,
and IF it matches, call that module.

  We *really* need a configuration file parser written in yacc/lex.
And we need a simple language to process requests.  OH well, one thing
at a time...

  Alan DeKok.

- 
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html

Reply via email to