I've found something odd in regard to the modules directory. I ended up needing to use checkval module for ldap authentication to work properly for me. the documentation I found said to place the following in config files: checkval { item-name = Calling-Station-Id check-name = Calling-Station-Id data-type = string notfound-reject = no } at the location I wanted the check to occur, but instead I ended up needing to use just: checkval because the above code was located in modules/checkval . The question is at this point, how could I, for example, have two different checkval checks? suppose I want to check an additional attribute? I recon I need a new file, but I'm not sure if it matters what I call the new file, or, for that matter, I'm not sure what to put inside the new file, except that I'm sure it must look very similar to that above. if someone could explain the specifics of this, or tell me where to find them explained, I would much appreciate the help. one more question: can there be multiples of ANY module specified? for example, can I use two different ldap or sql modules if I were to need to (just as a bad example, I propose: 1 radius server, 2 wlans with different user bases that can't be merged into one directory for whatever reasons).
On 01/17/2011 03:37 PM, Christ Schlacta wrote:
one more question: can there be multiples of ANY module specified?
In general modules can be instantiated multiple times under different names with configuration parameters unique to that name. Not sure if this is true for *all* modules though, there are probably some "singletons". -- John Dennis <jdennis@redhat.com> Looking to carve out IT costs? www.redhat.com/carveoutcosts/
On 2011/01/17 10:37 PM, Christ Schlacta wrote:
one more question: can there be multiples of ANY module specified? for example, can I use two different ldap or sql modules if I were to need to (just as a bad example, I propose: 1 radius server, 2 wlans with different user bases that can't be merged into one directory for whatever reasons).
The first instance of a module is defined (and called) using the module name e.g. Definition: checkval { item = .... .... } Calling the module: checkval The seconds instance is "named" and called using the "name" Definition: checkval blah { item = ... .... } Calling the module: blah Hope that helps. -- Johan Meiring Cape PC Services CC Tel: (021) 883-8271 Fax: (021) 886-7782
that does help. can the first instance be named as well, or must there always be an unnamed instance? On 1/17/2011 22:06, Johan Meiring wrote:
On 2011/01/17 10:37 PM, Christ Schlacta wrote:
one more question: can there be multiples of ANY module specified? for example, can I use two different ldap or sql modules if I were to need to (just as a bad example, I propose: 1 radius server, 2 wlans with different user bases that can't be merged into one directory for whatever reasons).
The first instance of a module is defined (and called) using the module name
e.g.
Definition: checkval { item = .... .... }
Calling the module: checkval
The seconds instance is "named" and called using the "name"
Definition: checkval blah { item = ... .... }
Calling the module: blah
Hope that helps.
participants (4)
-
Christ Schlacta -
Johan Meiring -
John Dennis -
Phil Mayers