Hi, Well, the reason we need to use an external program is because we need to authenticate the user against the calling-station-id attribute. This works fine when we modify the authorisation queries in sql.conf to check for this (in the 'where' condition). However, we're trying to account for a situation where the user has just subscribed to the service and his calling-station-id is not yet stored in the database. In this case we need to be able to update the database with the calling-station-id only after checking that the user exists, which is why using Exec-Program-Wait is great here.
All that the external program does is connect to the database, execute an update statement then disconnects. We were doing some more testing yesterday and it turns out the error we're getting back from Oracle is ORA-12154 which happens when it hits the connect statement. The error seems to refer to "Could not resolve service name". So now I'm wondering why it can't seem to resolve it since the program connects perfectly ok when executed on its own. Am I missing something here? Sally Fetouh > >Message: 11 >Date: Mon, 10 Jun 2002 12:20:24 -0500 >To: [EMAIL PROTECTED] >From: Chris Parker <[EMAIL PROTECTED]> >Subject: Re: Exec-Program-Wait >Reply-To: [EMAIL PROTECTED] > >At 07:18 AM 6/9/2002 +0400, Sally Fetouh wrote: >>Hi, >> >>We're trying to use the Exec-Program-Wait attribute to call an external >>program that is supposed to update an Oracle database table. The external >>program is written in proC and involves connecting to the database, >>executing an UPDATE statement then disconnecting. We're using freeradius >>0.5's snapshot dated 3 June 2002 on a Solaris 8 system. > >Any reason why not using FreeRADIUS talking to Oracle natively, rather >than through an external program? > >You can tailor the queries in 'sql.conf' to do whatever you need, I would >think. > >-Chris - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
