2641444 - SAP Jam Admin Area scoped OAuth client doesn't allow C4C feed integration

SAP Knowledge Base Article - Public

2641444 - SAP Jam Admin Area scoped OAuth client doesn't allow C4C feed integration

Symptom

  • Admin Area scoped OAuth client doesn't allow C4C feed integration
  • The feed integration between C4C and SAP Jam is not working when OAuth defined in admin area context.

Environment

  • SAP Jam

Resolution

When you define the C4C integration (OAuth client specifically) in the context of an administrative area, the feed integration between C4C and SAP Jam breaks.

Specifically, only the comments shared in C4C / business records in Jam are shown. No status updates etc. is created as a feed event - neither in SAP Jam nor in C4C; even though the feed settings are set correctly.

The feeds are created globally, thus "local" OAuth client doesn't have the proper permission to create these feed objects via API.

Use the admin area only to setup the business records & external application. OAuth Client & SAML Trusted IDP can be in company scope. Simply keeping SAML Trusted IDP & OAuth Client in the Company scope and moving the external application to admin area.

Note: The OAuth client in an admin area limits functionality, so this is expected behavior as posting outside the scope that the OAuth client allows would be considered a defect.

Keywords

SAP Jam C4C feed admin area Oauth   , KBA , LOD-SF-JAM-C4C , JAM/ C4C Integration , Problem

Product

SAP Jam Collaboration all versions