Re: using set role command in a logon trigger

From: "Sriram Kumar" <k.sriramkumar@xxxxxxxxx>
To: "Jared Still" <jkstill@xxxxxxxxx>
Date: Fri, 6 Apr 2007 20:57:34 +0530

Hi Jared,

My mistake. Thanks for pointing out the same.

My undestanding of the requirement was to allow/disallow a role if the user
is connected from a particular node/app and this can be implemented using
roles authenticated using packages and if we use this approach, triggers
are NOT required

have not tried myself by example seems to match Laura's requirement

Refer Creating Secure Application Roles under
http://download-uk.oracle.com/docs/cd/B19306_01/network.102/b14266/apdvntro.htm

I dont have access to a DB to test by looks like the approach would work

Best Regards

Sriram Kumar






On 4/6/07, Jared Still <jkstill@xxxxxxxxx> wrote:


On 4/4/07, Sriram Kumar <k.sriramkumar@xxxxxxxxx> wrote:
>
> Hi,
>
> There is this new feature in 10g that allows you to authenticate roles
> based on packages. You can use that feature for this situation of yours.
>
> create role <> identified using schema.package;
>
>

Actually that was new in 9i.  :)

I was playing with it on 9.2.0.7 just this morning.

It still doesn't work from a trigger however.

--
Jared Still
Certifiable Oracle DBA and Part Time Perl Evangelist

Follow-Ups:

Re: using set role command in a logon trigger
From: Paul Drake

References:
- using set role command in a logon trigger
  - From: laura pena
- Re: using set role command in a logon trigger
  - From: Sriram Kumar
- Re: using set role command in a logon trigger
  - From: Jared Still

Re: using set role command in a logon trigger

Other related posts: