Does anyone knows a way to remove the inherit from parent using a script and not having the Admin Access?
I'm currently devoping a script that needs to check for new objects that is going to be used by Users with RMCD access, and I only see in the help file that it can only be done by someone with Admin Access.
Please guide me to make sure is viable or not, which I think is NOT, but just in case.
Thanks.
SystemAdmin - Tue Mar 30 18:38:42 EDT 2010 |
|
Re: Unimaginable Way (How to remove the inherit from parent access)
llandale - Wed Mar 31 13:09:13 EDT 2010
You must have Admin control access in order to modify the access controls on a thing.
So no, normal users who lack 'A' access to the module will normally not be able to turn a module into 'Specific' access, to create a shared section. However, if they have 'A' access to a parent Object then they can do so for its children. That situation can happen when someone with 'A' access to the module (the module admin) changes access to an Object on behalf of the user.
Its too bad the old DOORS decided that 'shared' sections were the same as 'specific' access objects. They really should have come up with a better way.
|
|
Re: Unimaginable Way (How to remove the inherit from parent access)
SystemAdmin - Wed Mar 31 14:07:16 EDT 2010 llandale - Wed Mar 31 13:09:13 EDT 2010
You must have Admin control access in order to modify the access controls on a thing.
So no, normal users who lack 'A' access to the module will normally not be able to turn a module into 'Specific' access, to create a shared section. However, if they have 'A' access to a parent Object then they can do so for its children. That situation can happen when someone with 'A' access to the module (the module admin) changes access to an Object on behalf of the user.
Its too bad the old DOORS decided that 'shared' sections were the same as 'specific' access objects. They really should have come up with a better way.
Thanks for the information.
Anything else that could problably be magical, that will allow me to do the decription above is welcome.
Great Day.
|
|
Re: Unimaginable Way (How to remove the inherit from parent access)
Mathias Mamsch - Thu Apr 01 04:37:03 EDT 2010 SystemAdmin - Wed Mar 31 14:07:16 EDT 2010
Well, what I did was to modify the access to all object, and make them admin for a specific group, but still can not change the Inherit from Parent option, unless I have the module open in exclusive edit. I just wanted to be able to modify the access without limiting the access to the module.
Thanks for the information.
Anything else that could problably be magical, that will allow me to do the decription above is welcome.
Great Day.
|
|
Re: Unimaginable Way (How to remove the inherit from parent access)
SystemAdmin - Thu Apr 01 06:50:30 EDT 2010 Mathias Mamsch - Thu Apr 01 04:37:03 EDT 2010
There would be some really dark magic to fake the edit mode of the module (by manipulating the module handle directly in memory) but this could lead to all sorts of problems, therefore I would not recommend it ... What DOORS version are you using? Regards, Mathias
|
|
Re: Unimaginable Way (How to remove the inherit from parent access)
Mathias Mamsch - Thu Apr 01 07:56:12 EDT 2010 SystemAdmin - Thu Apr 01 06:50:30 EDT 2010
I'am using DOORS 8.3 and looking to upgrade to the newest 9.2
I was experimenting with the following code, which will remove the inheritance from the current Object in shared edit mode (provided you have control access). But I advise you NOT TO USE this in any productive environment, since it will probably corrupt your module.
Note that this code might only work on DOORS 8.2, maybe 8.3 ... On any other DOORS version it might yield bad effects.
Regards, Mathias
// WARNING: DONT USE THIS EXPERIMENTAL CODE! IT WILL
// MOST PROBABLY CAUSE DATA LOSS IN YOUR MODULE!
Module m = current
int add = (addr_ m) + 6533
int &ref = addr_ add
int x = ref
ref = ((x | 8) & 0xFFFFFFFC)
specific (current Object)
save m
ref = x
|
|