The attributes I've mentioned are either server domain or IP address. On Tue, Aug 14, 2012 at 10:17 AM, Alan DeKok <aland@deployingradius.com>wrote:
Diego Matute wrote:
"different authentication methods" I really mean different user data stores and different methods like an optional second factor. I can wrap everything is a custom auth module, however I will still need a way to know which data store to use.
I could use NAS, but that would require the client to declare their IP address.
Which is how RADIUS works.
I was hoping for a solution where the client IP is not known and the right thing is done based on some attributes not cumbersome for a client to supply.
Like... what? Some random attribute? Do you even know?
Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html