Skip to content

Troubleshoot errors with Resource Access Management

Error scenarios

All the possible error details like Http Status code, error code and messages are specified in Resource Access Management API Specification

General issues

Scenario: Policy activated, but not taking effect

Issue

Policy is activated, but somehow not taking the desired effect, i.e. APIs are not honoring the fine-grained access check on certain resources.

Cause

Policy enforcement for the given environment is not enabled.

Resolution

To enable or verify the Policy enforcement on a given environment, contact MindSphere support team. This enforcement may take up to 1 hour to reflect the change.

Scenario: Policy for resource subsections

Issue

For resource hierarchy scenarios, a user expects that a subsection of resources are given access through a single resource specified in the Policy.

Cause

The parameter value for Propagation Depth may not be set correctly.

Resolution

Set the Propagation Depth value as -1 so that the given resource and all its descendants are included in the eligible resources.

Any questions left?

Ask the community


Except where otherwise noted, content on this site is licensed under the MindSphere Development License Agreement.


Last update: July 29, 2022