(RADIATOR) Our Interesting Requirement for Radiator
Dan Melomedman
dmelomed at devonitnet.com
Wed May 15 19:27:00 CDT 2002
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.
--
Excessive functionality is a root to security disasters.
===
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.
More information about the radiator
mailing list