Hello John -
In your case I would suggest using Oracle stored procedures for your business rules.
There is a contributed module in the goodies directory called "AuthBy PLSQL" that you can use for this.
regards
Hugh
On Thursday, Jul 10, 2003, at 01:47 Australia/Melbourne, John McFadden wrote:
We use LDAP to do the basic userid/password authentication but intend to use one or more Oracle databases
to apply business rules as LDAP is not dynamic enough.
The PostAuthHook gives us a place to do that but I'm not sure if I should try to do it within Radiator or
via an external program call.
I'm a bit nervious about the Radiator/Perl SQL overhead.
Does the PostAuthHook require a new connection for each request or for each session or each user?
Or can I open the connection in a StartupHook (global var) then just share it in the PostAuthHook to do the required SQL query.
Since we're just doing queries I'm hoping to share one connection to minimize overhead. Any issues with concurrency if we do?
How do I detect the database is down and attempt to allocate a new connection?
Comments, suggestions?
Regards JLM
=== Archive at http://www.open.com.au/archives/radiator/ Announcements on [EMAIL PROTECTED] To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
NB: have you included a copy of your configuration file (no secrets), together with a trace 4 debug showing what is happening?
-- 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 [EMAIL PROTECTED] To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
