(RADIATOR) Stored procedures

[Mike McCauley]

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:mikem at open.com.au]
> Sent: Friday, 4 April 2003 1:38 PM
> To: queksteven at stsunpage.st.com.sg; Tim Ballingall
> Cc: owner-radiator at open.com.au; 'radiator at open.com.au'
> Subject: Re: (RADIATOR) Stored procedures
>
>
> Hello Tim,
>
> On Fri, 4 Apr 2003 01:19 pm, queksteven at stsunpage.st.com.sg wrote:
> > Hi,
> >
> > I suggest that u should not use the paremeters instead they are
> > expecting a recordset.
>
> queksteven at stsunpage. 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 <tim at mazda.com.au>   04/04/2003 08:41 AM
> > Sent by: owner-radiator at open.com.au
> >
> >
> >               To:  "'radiator at open.com.au'" <radiator at open.com.au>
> >               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
> >
> >
> >
> > <snip>
> >                 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                               mikem at open.com.au
Open System Consultants Pty. Ltd            Unix, 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 radiator-announce at open.com.au
To unsubscribe, email 'majordomo at open.com.au' with
'unsubscribe radiator' in the body of the message.