*This message was transferred with a trial version of CommuniGate(tm) Pro*
From: "Oscar L. Garzón" <[EMAIL PROTECTED]>
To: "Sergio González" <[EMAIL PROTECTED]>
Subject: Dynamic DBSource
Date: Tue, 28 Jan 2003 05:10:03 -0500
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
Importance:
I think this might be of interest to the people in this list. The IESG is
approving the base Diameter protocol. Diameter is expected to, eventually,
replace Radius (though that definitively won't happen overnight).
The attached message implies the RFC will be released any day now... if you
can'
> *This message was transferred with a trial version of CommuniGate(tm) Pro*
>
> >From: "Oscar L. Garzón" <[EMAIL PROTECTED]>
> >To: "Sergio González" <[EMAIL PROTECTED]>
> >Subject: Dynamic DBSource
> >Date: Tue, 28 Jan 2003 05:10:03 -0500
> >X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.29
I Added %R.tablename in my SQL statements and it's working wonderful, I can
handle username in a easier way, thanks a lot...
Now I have another question, is there a way to use Client-Identifier as a
variable, I mean %{Client-Identifier}, directly in the SQL Statements? for
example,
AuthSelect SE
> Now I have another question, is there a way to use Client-Identifier as a
> variable, I mean %{Client-Identifier}, directly in the SQL Statements? for
> example,
>
> AuthSelect SELECT USERNAME, PASSWORD FROM USER WHERE
> NASPROFILE="%{Client-Identifier}"
>
That should (IIRC) work fine, although
Hi All,
I hve upgraded to Radiator version 3.0 from 2.17. Radius is running on
Solaris and we r using openlink for database access.Every thing was
working fine ... but suddenly radiator stops and kills its process with
the following error
---
[OpenLink][ODBC][SQL Se
