Re: (RADIATOR) Stored procedures
Hello Tim,
On Fri, 4 Apr 2003 02:17 pm, Tim Ballingall wrote:
> Thanks for the feedback - appreciate it..
>
> Ultimately though, does this mean that I need a procedure that returns a
> recordset OR, modify AuthPLSQL to authenticate without the recordset and
> use the return code only...?
Well the choice is yours, but I would think changing the SP would be best,
because then you would not have to maintain your own local mods to AuthPLSQL.
OTOH, changing the AuthPLSQL.pm may be the quicker and easier course?
Cheers.
>
> FYI - I'm not worrying about attributes at this stage.
>
> Thanks again
>
> Tim
>
> -Original Message-
> From: Mike McCauley [mailto:[EMAIL PROTECTED]
> Sent: Friday, 4 April 2003 1:38 PM
> To: [EMAIL PROTECTED]; Tim Ballingall
> Cc: [EMAIL PROTECTED]; '[EMAIL PROTECTED]'
> Subject: Re: (RADIATOR) Stored procedures
>
>
> Hello Tim,
>
> On Fri, 4 Apr 2003 01:19 pm, [EMAIL PROTECTED] wrote:
> > Hi,
> >
> > I suggest that u should not use the paremeters instead they are
> > expecting a recordset.
>
> [EMAIL PROTECTED] is correct.
> We expect to get a recordset from the stored procedure if the user matches.
> If
> there is no match there should be no recordset returned.
>
> Hope that helps.
>
> Cheers.
>
> > Hope it help.
> >
> >
> >
> > Tim Ballingall <[EMAIL PROTECTED]> 04/04/2003 08:41 AM
> > Sent by: [EMAIL PROTECTED]
> >
> >
> > To: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>
> > cc: (bcc: QUEK Steven/Prod Dev Dir/STSunPage/ST Group)
> > Subject: (RADIATOR) Stored procedures
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > Hello all,
> >
> >
> > Can I start by saying how happy I was to come across such a flexible &
> > powerful product. Easily the most configurable Radius server I've ever
> > seen..:)
> >
> >
> > And on that note I'm actually evaluating Radiator at the moment.
> > If I can get it to do as I want I'll be a certain buyer. What I need
> > to do is to get Radiator running on an 2K Server machine, connecting
> > to a remote Tru64 Unix server running Oracle 8.0.5.1, and using a
> > stored oracle procedure to authenticate. Sqlnet is installed &
> > operating correctly on the 2K server. My stored procedure looks like :
> >
> >
> > procedure check_password
> > (db_user in varchar2,
> > db_password in varchar2,
> > db_valid_password out number)
> >
> >
> > After passing three parameters, it will return a value in
> > db_valid_password. If that value is 1 then the username password
> > match, any other value indicates a wrong combination.
> >
> >
> > Now I'm trying to get this to work using the sample plsql.cfg &
> > authplsql.pm but it's giving me a little grief... My config file looks
> > like
> >
> >
> >
> >
> > NoDefault
> > DBSource dbi:Oracle:MYMACHINE
> > DBUsername MYUSERNAME
> > DBAuth MYPASSWORD
> > # Authentication
> > AuthBlock BEGIN \
> > security_pkg.check_password
> > ('%n','%P',\
> >
> > :reply_item); \
> >
> > END;
> > AuthParamDef:reply_item,GENERIC,reply
> >
> >
> > My trace debug looks like :
> >
> >
> > Fri Apr 4 10:06:31 2003: DEBUG: Query is: BEGIN
> > security_pkg.check_password('SOMEUSER','SOMEPASSWORD',:reply_item);
> > END;
> >
> >
> > Fri Apr 4 10:06:31 2003: ERR: Bad attribute=value pair: 1 Fri Apr 4
> > 10:06:31 2003: DEBUG: Radius::AuthPLSQL looks for match with SOMEUSER
> > Fri Apr 4 10:06:31 2003: DEBUG: Radius::AuthPLSQL ACCEPT:
> > Fri Apr 4 10:06:31 2003: DEBUG: Access accepted for SOMEUSER
> >
> >
> > The trouble here is that "SOMEPASSWORD" is actually incorrect, but the
> > user is being authenticated anyway. I think I'm implementing AuthPLSQL
> > incorrectly but not entirely sure. Do I need to define the behavior of
> > check_password to Radiator...? If so, I'd appreciate some help on
> > where I would do this.
> >
> >
> > Any advice on this would be most welcome..
RE: (RADIATOR) Stored procedures
Thanks for the feedback - appreciate it..
Ultimately though, does this mean that I need a procedure that returns a
recordset OR, modify AuthPLSQL to authenticate without the recordset and use
the return code only...?
FYI - I'm not worrying about attributes at this stage.
Thanks again
Tim
-Original Message-
From: Mike McCauley [mailto:[EMAIL PROTECTED]
Sent: Friday, 4 April 2003 1:38 PM
To: [EMAIL PROTECTED]; Tim Ballingall
Cc: [EMAIL PROTECTED]; '[EMAIL PROTECTED]'
Subject: Re: (RADIATOR) Stored procedures
Hello Tim,
On Fri, 4 Apr 2003 01:19 pm, [EMAIL PROTECTED] wrote:
> Hi,
>
> I suggest that u should not use the paremeters instead they are
> expecting a recordset.
[EMAIL PROTECTED] is correct.
We expect to get a recordset from the stored procedure if the user matches.
If
there is no match there should be no recordset returned.
Hope that helps.
Cheers.
>
> Hope it help.
>
>
>
> Tim Ballingall <[EMAIL PROTECTED]> 04/04/2003 08:41 AM
> Sent by: [EMAIL PROTECTED]
>
>
> To: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>
> cc: (bcc: QUEK Steven/Prod Dev Dir/STSunPage/ST Group)
> Subject: (RADIATOR) Stored procedures
>
>
>
>
>
>
>
>
>
> Hello all,
>
>
> Can I start by saying how happy I was to come across such a flexible &
> powerful product. Easily the most configurable Radius server I've ever
> seen..:)
>
>
> And on that note I'm actually evaluating Radiator at the moment.
> If I can get it to do as I want I'll be a certain buyer. What I need
> to do is to get Radiator running on an 2K Server machine, connecting
> to a remote Tru64 Unix server running Oracle 8.0.5.1, and using a
> stored oracle procedure to authenticate. Sqlnet is installed &
> operating correctly on the 2K server. My stored procedure looks like :
>
>
> procedure check_password
> (db_user in varchar2,
> db_password in varchar2,
> db_valid_password out number)
>
>
> After passing three parameters, it will return a value in
> db_valid_password. If that value is 1 then the username password
> match, any other value indicates a wrong combination.
>
>
> Now I'm trying to get this to work using the sample plsql.cfg &
> authplsql.pm but it's giving me a little grief... My config file looks
> like
>
>
>
>
> NoDefault
> DBSource dbi:Oracle:MYMACHINE
> DBUsername MYUSERNAME
> DBAuth MYPASSWORD
> # Authentication
> AuthBlock BEGIN \
> security_pkg.check_password
> ('%n','%P',\
>
> :reply_item); \
>
> END;
> AuthParamDef:reply_item,GENERIC,reply
>
>
> My trace debug looks like :
>
>
> Fri Apr 4 10:06:31 2003: DEBUG: Query is: BEGIN
> security_pkg.check_password('SOMEUSER','SOMEPASSWORD',:reply_item);
> END;
>
>
> Fri Apr 4 10:06:31 2003: ERR: Bad attribute=value pair: 1 Fri Apr 4
> 10:06:31 2003: DEBUG: Radius::AuthPLSQL looks for match with SOMEUSER
> Fri Apr 4 10:06:31 2003: DEBUG: Radius::AuthPLSQL ACCEPT:
> Fri Apr 4 10:06:31 2003: DEBUG: Access accepted for SOMEUSER
>
>
> The trouble here is that "SOMEPASSWORD" is actually incorrect, but the
> user is being authenticated anyway. I think I'm implementing AuthPLSQL
> incorrectly but not entirely sure. Do I need to define the behavior of
> check_password to Radiator...? If so, I'd appreciate some help on
> where I would do this.
>
>
> Any advice on this would be most welcome...
>
>
> Thanks kindly in advance
>
>
> Tim
>
>
>
>
>
>
>***
>***
>
> Mazda Australia takes many precautions to ensure emails are virus
>free. For extra protection you should virus scan this message
>yourself.
>
***
>***
>
>
>
>
>
>
>
> [This e-mail is confidential and may also be privileged. If you are
> not the intended recipient, please delete it and notify us
> immediately; you should not copy or use it for any purpose, nor
> disclose its contents to any other person. Thank you.]
--
Mike McCauley [EMAIL PROTECTED]
Open System Consultants Pty. LtdUnix, Perl, Motif, C++, WWW
24 Bateman St
Re: (RADIATOR) Stored procedures
Hello Tim,
On Fri, 4 Apr 2003 01:19 pm, [EMAIL PROTECTED] wrote:
> Hi,
>
> I suggest that u should not use the paremeters instead they are expecting a
> recordset.
[EMAIL PROTECTED] is correct.
We expect to get a recordset from the stored procedure if the user matches. If
there is no match there should be no recordset returned.
Hope that helps.
Cheers.
>
> Hope it help.
>
>
>
> Tim Ballingall <[EMAIL PROTECTED]> 04/04/2003 08:41 AM
> Sent by: [EMAIL PROTECTED]
>
>
> To: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>
> cc: (bcc: QUEK Steven/Prod Dev Dir/STSunPage/ST Group)
> Subject: (RADIATOR) Stored procedures
>
>
>
>
>
>
>
>
>
> Hello all,
>
>
> Can I start by saying how happy I was to come across such a flexible &
> powerful product. Easily the most configurable Radius server I've ever
> seen..:)
>
>
> And on that note I'm actually evaluating Radiator at the moment. If I
> can get it to do as I want I'll be a certain buyer. What I need to do is to
> get Radiator running on an 2K Server machine, connecting to a remote Tru64
> Unix server running Oracle 8.0.5.1, and using a stored oracle procedure to
> authenticate. Sqlnet is installed & operating correctly on the 2K server.
> My stored procedure looks like :
>
>
> procedure check_password
> (db_user in varchar2,
> db_password in varchar2,
> db_valid_password out number)
>
>
> After passing three parameters, it will return a value in
> db_valid_password. If that value is 1 then the username password match, any
> other value indicates a wrong combination.
>
>
> Now I'm trying to get this to work using the sample plsql.cfg &
> authplsql.pm but it's giving me a little grief... My config file looks like
>
>
>
>
> NoDefault
> DBSource dbi:Oracle:MYMACHINE
> DBUsername MYUSERNAME
> DBAuth MYPASSWORD
> # Authentication
> AuthBlock BEGIN \
> security_pkg.check_password
> ('%n','%P',\
>
> :reply_item); \
>
> END;
> AuthParamDef:reply_item,GENERIC,reply
>
>
> My trace debug looks like :
>
>
> Fri Apr 4 10:06:31 2003: DEBUG: Query is: BEGIN
> security_pkg.check_password('SOMEUSER','SOMEPASSWORD',:reply_item); END;
>
>
> Fri Apr 4 10:06:31 2003: ERR: Bad attribute=value pair: 1
> Fri Apr 4 10:06:31 2003: DEBUG: Radius::AuthPLSQL looks for match with
> SOMEUSER
> Fri Apr 4 10:06:31 2003: DEBUG: Radius::AuthPLSQL ACCEPT:
> Fri Apr 4 10:06:31 2003: DEBUG: Access accepted for SOMEUSER
>
>
> The trouble here is that "SOMEPASSWORD" is actually incorrect, but the user
> is being authenticated anyway. I think I'm implementing AuthPLSQL
> incorrectly but not entirely sure. Do I need to define the behavior of
> check_password to Radiator...? If so, I'd appreciate some help on where I
> would do this.
>
>
> Any advice on this would be most welcome...
>
>
> Thanks kindly in advance
>
>
> Tim
>
>
>
>
>
> ***
>***
>
> Mazda Australia takes many precautions to ensure emails are virus free.
> For extra protection you should virus scan this message yourself.
> ***
>***
>
>
>
>
>
>
>
> [This e-mail is confidential and may also be privileged. If you are not the
> intended recipient, please delete it and notify us immediately; you should
> not copy or use it for any purpose, nor disclose its contents to any other
> person. Thank you.]
--
Mike McCauley [EMAIL PROTECTED]
Open System Consultants Pty. LtdUnix, Perl, Motif, C++, WWW
24 Bateman St Hampton, VIC 3188 Australia http://www.open.com.au
Phone +61 3 9598-0985 Fax +61 3 9598-0955
Radiator: the most portable, flexible and configurable RADIUS server
anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald,
Platypus, Freeside, TACACS+, PAM, external, Active Directory, EAP, TLS,
TTLS, PEAP etc on Unix, Windows, MacOS etc.
===
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.
Re: (RADIATOR) Stored procedures
Hi,
I suggest that u should not use the paremeters instead they are expecting a
recordset.
Hope it help.
Tim Ballingall <[EMAIL PROTECTED]> 04/04/2003 08:41 AM
Sent by: [EMAIL PROTECTED]
To: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>
cc: (bcc: QUEK Steven/Prod Dev Dir/STSunPage/ST Group)
Subject: (RADIATOR) Stored procedures
Hello all,
Can I start by saying how happy I was to come across such a flexible &
powerful product. Easily the most configurable Radius server I've ever
seen..:)
And on that note I'm actually evaluating Radiator at the moment. If I
can get it to do as I want I'll be a certain buyer. What I need to do is to
get Radiator running on an 2K Server machine, connecting to a remote Tru64
Unix server running Oracle 8.0.5.1, and using a stored oracle procedure to
authenticate. Sqlnet is installed & operating correctly on the 2K server.
My stored procedure looks like :
procedure check_password
(db_user in varchar2,
db_password in varchar2,
db_valid_password out number)
After passing three parameters, it will return a value in
db_valid_password. If that value is 1 then the username password match, any
other value indicates a wrong combination.
Now I'm trying to get this to work using the sample plsql.cfg &
authplsql.pm but it's giving me a little grief... My config file looks like
:
NoDefault
DBSource dbi:Oracle:MYMACHINE
DBUsername MYUSERNAME
DBAuth MYPASSWORD
# Authentication
AuthBlock BEGIN \
security_pkg.check_password
('%n','%P',\
:reply_item); \
END;
AuthParamDef:reply_item,GENERIC,reply
My trace debug looks like :
Fri Apr 4 10:06:31 2003: DEBUG: Query is: BEGIN
security_pkg.check_password('SOMEUSER','SOMEPASSWORD',:reply_item); END;
Fri Apr 4 10:06:31 2003: ERR: Bad attribute=value pair: 1
Fri Apr 4 10:06:31 2003: DEBUG: Radius::AuthPLSQL looks for match with
SOMEUSER
Fri Apr 4 10:06:31 2003: DEBUG: Radius::AuthPLSQL ACCEPT:
Fri Apr 4 10:06:31 2003: DEBUG: Access accepted for SOMEUSER
The trouble here is that "SOMEPASSWORD" is actually incorrect, but the user
is being authenticated anyway. I think I'm implementing AuthPLSQL
incorrectly but not entirely sure. Do I need to define the behavior of
check_password to Radiator...? If so, I'd appreciate some help on where I
would do this.
Any advice on this would be most welcome...
Thanks kindly in advance
Tim
**
Mazda Australia takes many precautions to ensure emails are virus free.
For extra protection you should virus scan this message yourself.
**
[This e-mail is confidential and may also be privileged. If you are not the
intended recipient, please delete it and notify us immediately; you should
not copy or use it for any purpose, nor disclose its contents to any other
person. Thank you.]
===
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.
(RADIATOR) Stored procedures
Title: Stored procedures
Hello all,
Can I start by saying how happy I was to come across such a flexible & powerful product. Easily the most configurable Radius server I've ever seen..:)
And on that note I'm actually evaluating Radiator at the moment. If I can get it to do as I want I'll be a certain buyer. What I need to do is to get Radiator running on an 2K Server machine, connecting to a remote Tru64 Unix server running Oracle 8.0.5.1, and using a stored oracle procedure to authenticate. Sqlnet is installed & operating correctly on the 2K server. My stored procedure looks like :
procedure check_password
(db_user in varchar2,
db_password in varchar2,
db_valid_password out number)
After passing three parameters, it will return a value in db_valid_password. If that value is 1 then the username password match, any other value indicates a wrong combination.
Now I'm trying to get this to work using the sample plsql.cfg & authplsql.pm but it's giving me a little grief... My config file looks like :
NoDefault
DBSource dbi:Oracle:MYMACHINE
DBUsername MYUSERNAME
DBAuth MYPASSWORD
# Authentication
AuthBlock BEGIN \
security_pkg.check_password('%n','%P',\
:reply_item); \
END;
AuthParamDef :reply_item, GENERIC, reply
My trace debug looks like :
Fri Apr 4 10:06:31 2003: DEBUG: Query is: BEGIN security_pkg.check_password('SOMEUSER','SOMEPASSWORD',:reply_item); END;
Fri Apr 4 10:06:31 2003: ERR: Bad attribute=value pair: 1
Fri Apr 4 10:06:31 2003: DEBUG: Radius::AuthPLSQL looks for match with SOMEUSER
Fri Apr 4 10:06:31 2003: DEBUG: Radius::AuthPLSQL ACCEPT:
Fri Apr 4 10:06:31 2003: DEBUG: Access accepted for SOMEUSER
The trouble here is that "SOMEPASSWORD" is actually incorrect, but the user is being authenticated anyway. I think I'm implementing AuthPLSQL incorrectly but not entirely sure. Do I need to define the behavior of check_password to Radiator...? If so, I'd appreciate some help on where I would do this.
Any advice on this would be most welcome...
Thanks kindly in advance
Tim
**
Mazda Australia takes many precautions to ensure emails are virus free.
For extra protection you should virus scan this message yourself.
**
Re: Fwd: Re: (RADIATOR) Stored procedures once again
Hello Pavel,
the way DBD-Oracle handles stored procedures is quite different to many (all?)
other DBD modules. The method you describe of working with SPs in Oracle is
correct, and therefore using Oracle stored procedures in Radiator would require
changing the code that gets the user details.
You dont say which platform you are on, but you might want to consider using
DBD-ODBC which allows you to say something like
exec functioname 'arg'
and get a row back into Radiator in the standard way.
Hope that helps.
Cheers.
>
> -- Forwarded Message --
> Subject: Re: (RADIATOR) Stored procedures once again
> Date: Fri, 30 Jun 2000 18:54:03 +0400
> From: "Pavel A. Crasotin" <[EMAIL PROTECTED]>
>
>
> I've checked Oracle PLSQL reference, DBD-Oracle manual.
> The correct syntax to call Oracle stored procedure/function from a perl
script is
> to wrap it in BEGIN END; block then call prepare(), bind_param[_inout]() for
IN and OUT
> parameters if any, than execute().
> To pass returned results (it can be OUT parameters in stored procedure) it
must be
> called "bind_param_inout" DBD function. The "exec..." will fail if DBD uses
OCI.
> The positional references work only with prefetched rows (result of @row =
$sth->fetchrow call)...
>
> I would like to use the stored procedure 'cause it's the best way to
implement
> access policy to our networks.
>
> May be I'm using wrong DBD-Oracle module?
>
> Does anyone use stored procedure to get password, check and reply items from
Oracle?
> I need advice how can it be done without rewriting Radiator?
>
> Thanx in advance,
> Pavel A. Crasotin
>
> Open Joint-Stock Company SeverTransCom
> 15, Yaroslavl, Sobinova 40/13
> Tel/Fax: +7 (0852) 72-17-28, 72-17-38
>
>
>
>
> >
> > Hello Pavel -
> >
> > On Fri, 30 Jun 2000, Pavel A. Crasotin wrote:
> > > Hi all,
> > >
> > > we have stored procedure get_user_details(uname, pwd, check, reply) in
Oracle8i which accepts
> > > username and returns password, check and reply items.
> > > Procedure works fine in the test Perl script.
> > >
> > > Can anyone help me and say what combinations of AuthSelect and
AuthColumnDef
> > > should I write to pass the returned parameters to Radiator for
proccessing?
> > >
> > > I've dug the mailng list but didnt find how to do this.
> > > The right syntax of AuthSelect should be
> > >
> > > AuthSelect begin get_user_details('%n', pwd, check, reply); end; I think.
> > > But I dont get how to bind the returned parameters to Radiator. Is it
possible?
> > >
> >
> > Here is an example from Radius/AuthRODOPI.pm:
> >
> > "exec Interface_VircomUsers '$name'"
> >
> > I would have expected you to define something similar for your AuthSelect.
> >
> > As to dealing with the returned values, the AuthColumnDef's have positional
> > references for the first, second, third, etc. values returned by the
> > AuthSelect. Therefore you would have something like this (you will have to
> > experiment a bit no doubt):
> >
> > AuthSelect exec get_user_details '%n'
> >
> > AuthColumnDef 0, User-Password, check
> > AuthColumnDef 1, GENERIC, check
> > AuthColumnDef 2, GENERIC, reply
> >
> > Have a look at sections 6.25.6 and 6.25.7 in the Radiator 2.16.1 reference
> > manual.
> >
> > hth
> >
> > Hugh
> >
> > --
> > Radiator: the most portable, flexible and configurable RADIUS server
> > anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald,
> > Platypus, Freeside, Interbiller, TACACS+, PAM, external, etc, etc.
> > Available on Unix, Linux, FreeBSD, Windows 95/98/2000, NT, MacOS X.
> >
> >
> >
> > ===
> > Archive at http://www.starport.net/~radiator/
> > Announcements on [EMAIL PROTECTED]
> > To unsubscribe, email '[EMAIL PROTECTED]' with
> > 'unsubscribe radiator' in the body of the message.
> >
> ---
>
> --
> Radiator: the most portable, flexible and configurable RADIUS server
> anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald,
> Platypus, Freeside, Interbiller, TACACS+, PAM, external, etc, etc.
> Available on Unix, Linux, FreeBSD, Windows 95/98/2000, NT, MacOS X.
>
>
>
>-- End of excerpt from Hugh Irvine
--
Mike McCauley [EMAIL PROTECTED]
Open System Consultants Pty. LtdUnix, Perl, Motif, C++, WWW
24 Bateman St Hampton, VIC 3188 Australia http://www.open.com.au
Phone +61 3 9598-0985 Fax +61 3 9598-0955
Radiator: the most portable, flexible and configurable RADIUS server
anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald,
Platypus, Freeside, TACACS+, PAM, external, Active Directory etc etc
on Unix, Win95/8, 2000, NT, MacOS 9, MacOS X
===
Archive at http://www.starport.net/~radiator/
Announcements on [EMAIL PROTECTED]
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
Re: (RADIATOR) Stored procedures once again
I've checked Oracle PLSQL reference, DBD-Oracle manual.
The correct syntax to call Oracle stored procedure/function from a perl script is
to wrap it in BEGIN END; block then call prepare(), bind_param[_inout]() for IN and OUT
parameters if any, than execute().
To pass returned results (it can be OUT parameters in stored procedure) it must be
called "bind_param_inout" DBD function. The "exec..." will fail if DBD uses OCI.
The positional references work only with prefetched rows (result of @row =
$sth->fetchrow call)...
I would like to use the stored procedure 'cause it's the best way to implement
access policy to our networks.
May be I'm using wrong DBD-Oracle module?
Does anyone use stored procedure to get password, check and reply items from Oracle?
I need advice how can it be done without rewriting Radiator?
Thanx in advance,
Pavel A. Crasotin
Open Joint-Stock Company SeverTransCom
15, Yaroslavl, Sobinova 40/13
Tel/Fax: +7 (0852) 72-17-28, 72-17-38
>
> Hello Pavel -
>
> On Fri, 30 Jun 2000, Pavel A. Crasotin wrote:
> > Hi all,
> >
> > we have stored procedure get_user_details(uname, pwd, check, reply) in Oracle8i
>which accepts
> > username and returns password, check and reply items.
> > Procedure works fine in the test Perl script.
> >
> > Can anyone help me and say what combinations of AuthSelect and AuthColumnDef
> > should I write to pass the returned parameters to Radiator for proccessing?
> >
> > I've dug the mailng list but didnt find how to do this.
> > The right syntax of AuthSelect should be
> >
> > AuthSelect begin get_user_details('%n', pwd, check, reply); end; I think.
> > But I dont get how to bind the returned parameters to Radiator. Is it possible?
> >
>
> Here is an example from Radius/AuthRODOPI.pm:
>
> "exec Interface_VircomUsers '$name'"
>
> I would have expected you to define something similar for your AuthSelect.
>
> As to dealing with the returned values, the AuthColumnDef's have positional
> references for the first, second, third, etc. values returned by the
> AuthSelect. Therefore you would have something like this (you will have to
> experiment a bit no doubt):
>
> AuthSelect exec get_user_details '%n'
>
> AuthColumnDef 0, User-Password, check
> AuthColumnDef 1, GENERIC, check
> AuthColumnDef 2, GENERIC, reply
>
> Have a look at sections 6.25.6 and 6.25.7 in the Radiator 2.16.1 reference
> manual.
>
> hth
>
> Hugh
>
> --
> Radiator: the most portable, flexible and configurable RADIUS server
> anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald,
> Platypus, Freeside, Interbiller, TACACS+, PAM, external, etc, etc.
> Available on Unix, Linux, FreeBSD, Windows 95/98/2000, NT, MacOS X.
>
>
>
> ===
> Archive at http://www.starport.net/~radiator/
> Announcements on [EMAIL PROTECTED]
> To unsubscribe, email '[EMAIL PROTECTED]' with
> 'unsubscribe radiator' in the body of the message.
>
===
Archive at http://www.starport.net/~radiator/
Announcements on [EMAIL PROTECTED]
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
Re: (RADIATOR) Stored procedures once again
Hello Pavel -
On Fri, 30 Jun 2000, Pavel A. Crasotin wrote:
> Hi all,
>
> we have stored procedure get_user_details(uname, pwd, check, reply) in Oracle8i
>which accepts
> username and returns password, check and reply items.
> Procedure works fine in the test Perl script.
>
> Can anyone help me and say what combinations of AuthSelect and AuthColumnDef
> should I write to pass the returned parameters to Radiator for proccessing?
>
> I've dug the mailng list but didnt find how to do this.
> The right syntax of AuthSelect should be
>
> AuthSelect begin get_user_details('%n', pwd, check, reply); end; I think.
> But I dont get how to bind the returned parameters to Radiator. Is it possible?
>
Here is an example from Radius/AuthRODOPI.pm:
"exec Interface_VircomUsers '$name'"
I would have expected you to define something similar for your AuthSelect.
As to dealing with the returned values, the AuthColumnDef's have positional
references for the first, second, third, etc. values returned by the
AuthSelect. Therefore you would have something like this (you will have to
experiment a bit no doubt):
AuthSelect exec get_user_details '%n'
AuthColumnDef 0, User-Password, check
AuthColumnDef 1, GENERIC, check
AuthColumnDef 2, GENERIC, reply
Have a look at sections 6.25.6 and 6.25.7 in the Radiator 2.16.1 reference
manual.
hth
Hugh
--
Radiator: the most portable, flexible and configurable RADIUS server
anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald,
Platypus, Freeside, Interbiller, TACACS+, PAM, external, etc, etc.
Available on Unix, Linux, FreeBSD, Windows 95/98/2000, NT, MacOS X.
===
Archive at http://www.starport.net/~radiator/
Announcements on [EMAIL PROTECTED]
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
(RADIATOR) Stored procedures once again
Hi all,
we have stored procedure get_user_details(uname, pwd, check, reply) in Oracle8i which
accepts
username and returns password, check and reply items.
Procedure works fine in the test Perl script.
Can anyone help me and say what combinations of AuthSelect and AuthColumnDef
should I write to pass the returned parameters to Radiator for proccessing?
I've dug the mailng list but didnt find how to do this.
The right syntax of AuthSelect should be
AuthSelect begin get_user_details('%n', pwd, check, reply); end; I think.
But I dont get how to bind the returned parameters to Radiator. Is it possible?
We use DBD-Oracle-1.03, Oracle8i on Sun Sparc Soalris.
With respect,
Pavel A. Crasotin
Open Joint-Stock Company SeverTransCom
15, Yaroslavl, Sobinova 40/13
Tel/Fax: +7 (0852) 72-17-28, 72-17-38
===
Archive at http://www.starport.net/~radiator/
Announcements on [EMAIL PROTECTED]
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
Re: (RADIATOR) Stored Procedures
On Mar 19, 11:24pm, John Abbott wrote: > Subject: (RADIATOR) Stored Procedures > Hi, > > Has anyone considered using stored procedures under oracle to execute a query and return one result. It would reduce a lot of the chatter between the radius server and db server(oracle in this case). It would also mean a single query send from the radius server could be translated into several queries on the oracle server. We have used a similar technique to talk to Rodopi with stored procedures. Theres no reason why you could not have an AuthSelect that calls an Oracle stored procedure. Cheers. -- Mike McCauley [EMAIL PROTECTED] Open System Consultants Pty. LtdUnix, Perl, Motif, C++, WWW 24 Bateman St Hampton, VIC 3188 Australia Consulting and development Phone, Fax: +61 3 9598-0985 http://www.open.com.au Radiator: the most portable, flexible and configurable RADIUS server anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald, Platypus, Freeside, external, etc etc on Unix, Win95/8, NT, Rhapsody === To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
(RADIATOR) Stored Procedures
Hi, Has anyone considered using stored procedures under oracle to execute a query and return one result. It would reduce a lot of the chatter between the radius server and db server(oracle in this case). It would also mean a single query send from the radius server could be translated into several queries on the oracle server. Regs John === To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
