3774027 - HTTP API connection technical user issue

- SAC OAuth Client Credentials are configured for an HTTP API connection to integrate SAP Analytics Cloud (SAC) with an external API .
- Despite successful API call execution through the SAC connection, workflow execution on the Alteryx/KONG side displays the local/personal SAC user instead of the technical OAuth user.

SAP ANALYTICS CLOUD

Expected behavior.

When using an HTTP API connection with OAuth 2.0 Client Credentials, SAC authenticates using the technical OAuth client and sends requests using the generated access token. This flow is designed for system-to-system communication and does not include or propagate any end-user identity.

Given this, SAC does not send any personal or local user information as part of the API request.

The behavior you are observing where the execution in Alteryx/KONG shows a personal SAC user originates from the backend side. This indicates that the user identity is being determined or mapped within your KONG / Alteryx setup.

Therefore, the issue is not related to SAC but to how the backend system processes the incoming request and assigns user identity.

SAC,Alteryx,KONG,backend,system,OAuth,client , KBA , LOD-ANA-PL-MA , Multi Actions , Problem