SAP Knowledge Base Article - Preview

3829986 - Joule Work Mobile App / SAP Start — Selective HTTP 401 "Logon failed" on Dynamic Data OData Requests Through SAP Build Work Zone

Symptom

When using the Joule Work mobile app (formerly SAP Mobile Start) or SAP Start connected to SAP Build Work Zone, standard edition, with an SAP S/4HANA Cloud Private Edition backend via Cloud Connector and Principal Propagation:

  • Some tile dynamic data requests succeed (HTTP 200) while others fail with HTTP 401 "Logon failed".
  • Failed requests return an ABAP-style HTML login failure page as the response body.
  • Tile icons may fail to load (iconCouldNotBeLoaded / iconNotAvailable).
  • The "SAP-icons" font may fail to register.
  • Tile data shows "dataIsInvalid" or "OAuth2Error.tokenRejected".
  • The same behavior occurs on desktop browser (SAP Build Work Zone site), confirming the issue is not specific to the mobile app.
  • The customer may also report "Not Found" when accessing the S/4HANA runtime URL from the Work Zone site.


Read more...

Environment

  • Joule Work mobile app (formerly SAP Mobile Start) — any version
  • SAP Build Work Zone, standard edition
  • SAP S/4HANA Cloud Private Edition backend
  • SAP Cloud Connector with Principal Propagation (X.509 certificate, CERTRULE)
  • Three-destination pattern: design-time (BasicAuthentication), runtime (PrincipalPropagation), dynamic data (PrincipalPropagation + HTML5.DynamicDestination=true)

Keywords

Joule Work, SAP Mobile Start, Build Work Zone, S/4HANA Private Edition, HTTP 400, RecommendationService, InterestCardsService, icon loading, SAP-icons, Theme Manager, ICF activation, SICF, principal propagation, dynamic data destination, HTTP 401 , KBA , MOB-APP-SMS , SAP Mobile Start , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.