Hi list,
We are authenticating users against an Oracle database and there is a
particular Radiator (at least I assume it's Radiator) behaviour which we
would like to eliminate.
Concerning users with null passwords (i.e. a database null in the
password field. When a password is supplied and the
Pual and Hugh,
We initially have the same problem as Hugh described; i.e., a
situation with duplicate NAS-Identifier + NAS-port. The way to get around
is to generate a session id based on NAS-Identifier + NAS-port +
DATE:HH24-MI-SS. This should guarantee uniqueness unless you get
multiple
Richard,
Could it be something as simple as the following?
select decode(user, username, 'ACCEPT', 'DENIED')
from user_table
where user = username and pass = password;
username and password are sent from radiator to the Oracle
DB. user and pass are username and
Hello Richard -
This is the expected behaviour. If you want to change this you will need to supply an AuthSelect statement that does something different.
See section 6.28.6 in the Radiator 3.6 reference manual (doc/ref.html).
Here is the relevant point:
If the password (or encrypted password)
Hello Geoffrey,
On Fri, 25 Jul 2003 09:42 am, Hugh Irvine wrote:
Hello Geoffrey -
On Thursday, Jul 24, 2003, at 19:40 Australia/Melbourne, DUFOUR
Geoffrey wrote:
Hello,
As far as I understand, radiusd reads the configuration file only once
(when it starts). Correct ?
Correct
