(RADIATOR) Our Interesting Requirement for Radiator

[Hugh Irvine]

Hello Dan -

You should be able to do what you require quite easily with a custom 
"SearchFilter" and the "Expiration" check item.

Have a look at sections 6.35.13 and 13.1.4 in the Radiator 3.0 manual.
("doc/ref.html").

regards

Hugh


On Thu, 16 May 2002 10:27, Dan Melomedman wrote:
> Hi. Here's what required by our installation. We have our account entries
> in the LDAP directory. Every account can be authenticated using RADIUS for
> several services like VPN tunnels, dial-up etc. There needs to be an
> expirattion date for each type of service. IOW there's a different
> expiration date attribute for each RADIUS-authenticated service. From what
> I've read in the docs, Radiator only supports one expiration attribute per
> directory entry natively. We need an ability to configure a separate
> expiration date attribute for each sevice an LDAP entry could authenticate.
> Is there any way we can achieve what I've described above? Thanks much.

-- 
Radiator: the most portable, flexible and configurable RADIUS server
anywhere. Available on *NIX, *BSD, Windows 95/98/2000, NT, MacOS X.
-
Nets: internetwork inventory and management - graphical, extensible,
flexible with hardware, software, platform and database independence.
===
Archive at http://www.open.com.au/archives/radiator/
Announcements on radiator-announce at open.com.au
To unsubscribe, email 'majordomo at open.com.au' with
'unsubscribe radiator' in the body of the message.