Re: Limiting a user to one concurrent session at a time

Dale E. Reed Jr. (daler@iea.com)
Sun, 01 Dec 1996 13:07:31 -0800

Stephen Zedalis wrote:
>
> On Sat, 30 Nov 1996, Terry W. Stroud wrote:
>
> > I am using two pm2e30's and RadiusNT for authentication. I want to limit a
> > username to one concurrent session at a time. I have read about the -R
> > command but have had no success with it. Can anyone help with this issue??
>
> I would suggest contacting the author of RadiusNT. Limiting multiple
> logins is not a feature of Livingston Radius 1.16 or 2.0 (darn it). Yet
> another RFE that never made the light of day but has always been in
> "the next version of RADIUS"

I guess thats me. :) -R only works when you are in ODBC enabled mode.
We chose not to support single server concurrency control, because there
is two many problems with state control. With a true RDBMS database
on the backend the -R concurrency control allows multiple servers to
maintain state between each other as well as when it is re-started.
A very elegant solution, especially for large installations.

There is an example MS Access database which is included with RadiusNT
called Radius7.mdb. This has everything you need. After creating an
ODBC DSN called "radius" pointing to the Access database, start
RadiusNT like this:

radius -x -b -R3

If you want to allow configurable limits in the database, change -R3 to
-R67. Also, make sure you are running 1.16.49, since there were a
couple
of fixes for MS Access databases in that release.

-- 
Dale E. Reed Jr.  (daler@iea.com)
_____________________________________________________________________
 Internet Engineering Associates   |  RadiusNT, Emerald, and NT FAQs
  Internet Solutions for Today     |    http://www.emerald.iea.com