Alexandre Chapellon wrote:
I have an oracle database storing authentication information for thousounds of differents users. This database is of course, not compliant at all with freeradius requirements (users file like). What is the best practice to make it work.
You can edit the default SQL queries. That's why they're in a configuration file.
I have many attributes to manage in checks as well in replys, such as simultaneous-use, counters, ippools, session-timeout,traffic-limit etc... I though using views to achieve compliance with freeradius tables specs, but maybe there is a better solution.
If you're just looking for username -> password, editing the SQL queries is fine. If you're adding lots of attributes based on a complex existing schema, another method like views is best. Alan DeKok.