topic Re: Regarding autorization object in Application Development and Automation Discussions

Regarding autorization object

Former Member — Tue, 08 Apr 2008 03:37:25 GMT

Hi,

I have a single role called xyz ,i need to use that role around 100 organisation and also i need to filter according to their respective organisation.How is it possible.Kindly recommmend a solution.

Regards

sekar.

Re: Regarding autorization object

Former Member — Tue, 08 Apr 2008 05:16:14 GMT

from the info fiven i suggest to create a template (basis) role and derive that 100 times.

Re: Regarding autorization object

Former Member — Tue, 08 Apr 2008 09:35:31 GMT

Hello,

Please use the base role derived concept where in Base role will have org values as * and dervied roles will have your defined org values.

Re: Regarding autorization object

Former Member — Tue, 08 Apr 2008 20:05:28 GMT


> Hello,
> Please use the base role derived concept where in Base role will have org values as * and dervied roles will have your defined org values.

The base/master/parent role does not need to have * as org values, lots of places leave them blank.

Re: Regarding autorization object

Former Member — Tue, 08 Apr 2008 21:21:40 GMT

I would agree with Alex.

I am not a fan of derived roles, but from that little bit which I do know this * would also "blurr" the fields which are OrgLevel fields from the others which you might have maintained as * because you don't want to use them as a control in your concept.

Or do OrgLevel fields have a special colour or some other identification in the master role?

Cheers,

Julius

Re: Regarding autorization object

Former Member — Wed, 09 Apr 2008 05:09:19 GMT

Yes u r correct, org values can be left as blank.There is no separate color for org values in Master Role..

Julius i am not sure why are not fan of derived role concept as this is widely accepted concept in terms of security....

Re: Regarding autorization object

Former Member — Wed, 09 Apr 2008 06:23:02 GMT

Hi Anil,

Derived roles are widely accepted, as are composite roles and having manual & changed status authorisation objects. It doesn't necessarily mean that they are the right thing to do. Sure, there is a time and a place for them (when we are only deriving at Org Level - quite possibly this scenario) but they can cause plenty of problems if used to support a design which doesn't lend itself to this technique.

Cheers

Alex