cancel
Showing results for 
Search instead for 
Did you mean: 
Security Alert Log4j Security Vulnerability. Click here to know more.
cancel
Showing results for 
Search instead for 
Did you mean: 

Source: Project Permissions do not seem to inherit to shared subprojects (checkpointing)

ssaul
15-Moonstone

Source: Project Permissions do not seem to inherit to shared subprojects (checkpointing)

Project Permissions do not seem to inherit to shared subprojects.
When doing a project checkpoint or snapshot, the ACL of the original location of the shared subproject has to be changed to avoid permission denied errors.
(Where) is this documented?
We are working with shared subprojects very much and getting frequent errors when it comes to checkpointing.

In addition, the affected shared subproject is not shown in the permission denied error message, only the main project. So debugging this error is really hard.

 

Any advice?

1 ACCEPTED SOLUTION

Accepted Solutions
awalsh
17-Peridot
(To:ssaul)

The behaviour of the permissions (ACLs) is documented in the online help: 

https://support.ptc.com/cs/help/integrity_hc/integrity112_hc/en/IntegrityHelp/client_proj_adding_sha...

"When working with shared subprojects, Integrity Lifecycle Manager uses the actual name of the subproject in the repository rather than its relative name in the project hierarchy for the purposes of resolving ACLs, policy statements, event triggers, and change package entries. This enhances the portability of change packages across different projects."

 

With regards to checkpoint errors, its a defect if the subproject path is not being given in the permissions error message. This defect should have been fixed in 10.6. If you are using 10.6 or higher, please contact PTC Technical Support to submit a defect.  

 

View solution in original post

2 REPLIES 2
awalsh
17-Peridot
(To:ssaul)

The behaviour of the permissions (ACLs) is documented in the online help: 

https://support.ptc.com/cs/help/integrity_hc/integrity112_hc/en/IntegrityHelp/client_proj_adding_sha...

"When working with shared subprojects, Integrity Lifecycle Manager uses the actual name of the subproject in the repository rather than its relative name in the project hierarchy for the purposes of resolving ACLs, policy statements, event triggers, and change package entries. This enhances the portability of change packages across different projects."

 

With regards to checkpoint errors, its a defect if the subproject path is not being given in the permissions error message. This defect should have been fixed in 10.6. If you are using 10.6 or higher, please contact PTC Technical Support to submit a defect.  

 

View solution in original post

ssaul
15-Moonstone
(To:awalsh)

Thanks for the info - we are still at 10.5 and I did not see this in the version history.

 

While this won't help for the basic permission problem in shared subprojects, it will definitively help locating the problem.

Announcements

Windchill RVS Users


Please take our

Windchill RV&S Authoring with Formula Editor Survey