I now need to look at how I use RadiusNT with our SQL provisioning
application. Looking at te documentation and the debug output whilst in
operation, it appears we are locked into at least some of the RadiusNT
ie. The SQL statement to check for duplicate logins seems to use table and
column names hardcoded into RadiusNT rather than picking them from registry
settings on startup.
Our master and subaccount tables have different names and the primary keys
are based on columns of different types and names.
Any general advice for mixing it with a 3rd party schema?
2Day Internet Limited.