The users under one of my Execute ACL can able to execute the IS service by doing to “Trace to here”, “Trace”, “Step Into” . When i set my execute ACL to IS Service, Access denied message comes to only “Run” option, all the other options are letting the user to execute the service. IS it a product bug or is there any other way around to fix this problem?
The users who doesn’t belong to one of my Execute ACL can able to execute the IS service by doing “Trace to here”,
“Trace”, “Step Into” . Access denied message comes to only “Run” option, all the other options are letting the user
(who don’t belong to execute acl) to execute the service. IS it a product bug or is there any other way around to
fix this problem?
In prod, Our customer is expecting the developer list,read access. So they could able to trace/step into the service, how do we stop this now ?