Understanding Access Control issues

Typically, aPriori Professional displays an informative error message and adds it to the message tree whenever it denies access to an object. Therefore, as a best practice, fully review messages and logs when you experience issues while using aPriori Professional

An example of an error message you might see is shown in this figure.

The related message that might appear in the message tree is shown in this figure.

aPriori also appends detailed information about access denials to the log file, as shown in this figure.

TIP: If you are not comfortable trying to read and interpret log files, ask your aPriori administrator to use the following procedures to understand the situation you are encountering.

In specific circumstances, aPriori Professional aborts after reporting the first error for an action. For example, if you try to deep-cost an assembly that contains child components for which you do not have Read access, aPriori Professional displays a message about the first such component and then aborts the deep costing action. It does not provide error messages about other non-readable components in the assembly. For more information, see Access Control principles.

For security reasons, aPriori cannot always provide detailed information about access denial situations to identify exactly what target resource has failed which access check. For example, if there is a proprietary or otherwise sensitive component in an assembly that a group of users is not allowed to see, then it would be appropriate for Access Control to provide a detailed message sure as: "You do not have permission to read SecretComponentXYZ."