SAP Knowledge Base Article - Public

2901506 - SCIM Team API Breaks when Orca Content Namespace changed SAP Analytics Cloud (SAC) & SAP Digital Boardroom

Symptom

The following behavior occurs in SAP Analytics Cloud (SAC):

  • SCIM Team API Breaks when Orca Content Namespace changed.
  • Assignment status Failed.
  • Privileges for SAC system are in failed state. Only privilege/role is assigned correctly.

Environment

SAP Analytics Cloud (Enterprise) 2020.5.2

Reproducing the Issue

  1. In SAC, navigate to Security -> Teams and create a new team "TEAM1" (or any unique name).
  2. Navigate to System -> Administration -> System Configuration page.
  3. Click Edit button (pencil icon) and change Content Namespace to anything different (e.g. t.3 or t.TEST2) and Save.
  4. Return to the teams page and create another new team "TEAM2".
  5. Using the SCIM API, send requests:
    1. GET .../api/v1/scim/Groups/
    2. GET .../api/v1/scim/Groups/TEAM1
    3. GET .../api/v1/scim/Groups/TEAM2

Cause

Namespace changing.

Resolution

This issue is currently under investigation by development.

Workaround:

Delete all teams, then create new teams. The API then works 'directly to the team' and then can call a team to see who are it's members.

See Also

Your feedback is important to help us improve our knowledge base.

Keywords

SAP Cloud for Planning, , SAC, SAP AC, Cloud-Analytics, CloudAnalytics, SAPCloudAnalytics,Error, Issue, System, Data, User, Unable, Access, Connection, Sac, Connector, Story, Tenant, Import, Failed, Using, Working, SAML, SSO, sapanalyticscloud, sap analytical cloud, sap analytical cloud, SAC, Assignment of privileges and roles failed, Orca, Namespace, SCIM, Assignment status Failed, Privilege assignment failed, Role assignment failed,  Identity Management , KBA , LOD-ANA-DES , Model, Story Design & Visualizations , Problem

Product

SAP Analytics Cloud 1.0