Re: OAS 4.0 - PLSQL cartridge & Custom (application based) Security problem
Date: 1999/02/25
Message-ID: <7b2beb$ofq$1_at_nnrp1.dejanews.com>#1/1
Hi there-
From what I understand, the security model is done on a per-schema basis. You can set up the appropriate packages within the particular schema that you want to use custom authentication, "over-riding" the public synonyms.
...jeff
jeff grant, it manager, nettwerk productions vancouver, bc, canada
http://www.nettwerk.com http://www.nettweb.com
In article <7av478$64d$1_at_garnet.nbnet.nb.ca>,
"Armand Melanson" <melanson.armand_at_mit-it.com> wrote:
>
> Anyone have any experience implementing application based security on OAS
> running multiple PLSQL applications?Is it possible to specify different
> custom security models for different applications using the PLSQL cartridge?
> Is it possible to have 1 application use custom while another doesn't?
> When implementing custom security, you supply the package body for the
> OAS_PUBLIC.owa_custom indicating which security model to implement. However,
> once you specify the type( e.g. per_package), it appears that all the
> applications using the PLSQL cartridge must implement code to use this
> model - they must define an authorize function which handles the
> authentication. The seems ludicrous but the OAS documentation is rather
> scant on the subject & my experience has forced me to add authorize
> functions to all other applications using plsql cartridge for them to work.
>
>
-----------== Posted via Deja News, The Discussion Network ==---------- http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own Received on Thu Feb 25 1999 - 00:00:00 CET