It's all about the answers!

Ask a question

ACL for Work Items doesn't seem to be working fine in 2.0


Adil Chahid (45524118) | asked Aug 20 '09, 7:06 p.m.
Hi all,

as mentioned in a previous post, we've emulated the migration process by actually migrating a copy of our RTC 1.0.1.1 production database to our RTC 2.0 lab environment.

We even did link the RTC 2.0 lab instance to an RQM 2.0 lab instance.

We then created a Defect from RQM to RTC.
I decided to secure that project in RTC.

When I tried to access that WI with an unauthorized user, I was amazed to see that I was able to open that WI .

So I've tried other ACL restriction methods like actually using Members of the project area hierarchy and the Users in the access list only.
This "unwelcomed" user was neither part of the project nor from the access list and he was still able to access the "secret" Work Item.

The weird thing is that after creating a new WI from RTC (after applying the ACL security) that user was not able to access that WI as it should be!

So the security will only be applied to new artifacts that were created into the repository after the application of the ACL security ?

All the prior WI will still be accessble by everyone?

Please advise.

3 answers



permanent link
Patrick Streule (4.9k21) | answered Aug 21 '09, 8:22 a.m.
JAZZ DEVELOPER
So the security will only be applied to new artifacts that were
created into the repository after the application of the ACL security
?

All the prior WI will still be accessble by everyone?

The settings apply for all artifacts. The context id that is used to
determine the access right is set to all items during the migration. Were
there any errors during the migration?

--
Regards,
Patrick
Jazz Work Item Team

permanent link
Adil Chahid (45524118) | answered Aug 21 '09, 3:28 p.m.
So the security will only be applied to new artifacts that were
created into the repository after the application of the ACL security
?

All the prior WI will still be accessble by everyone?

The settings apply for all artifacts. The context id that is used to
determine the access right is set to all items during the migration. Were
there any errors during the migration?

--
Regards,
Patrick
Jazz Work Item Team


Hi Patrick,
we had no error during the migration it worked flawlessly once we determined the right DB2 setting.


Imported 660518 items, 1228337 item states in 34118106 ms. 6194 item states skipped. Error importing 0 elements.
...
Migration completed successfully.


So do you have any advice on that?
Thanks,

permanent link
Patrick Streule (4.9k21) | answered Aug 22 '09, 5:39 a.m.
JAZZ DEVELOPER
we had no error during the migration it worked flawlessly once we
determined the right DB2 setting.
Imported 660518 items, 1228337 item states in 34118106 ms. 6194 item
states skipped. Error importing 0 elements.
..
Migration completed successfully.
So do you have any advice on that?

I would suggest that you create a work item for this issue so we can
investigate and continue the discussion there.

--
Regards,
Patrick
Jazz Work Item Team

Your answer


Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.