Symptom
Below is the list of symptoms which can be seen while triggering the Iflow in SAP Cloud Platform Integration.
- Inbound connection to Iflow in Cloud Platform Integration fails with 401 error code when tried with S-user via Basic Authentication where BTP subaccount type is Neo.
- Same credentials for S-user is working fine for another subaccount and for "https://accounts.sap.com" for Basic Authentication.
- Status code- 401 Unauthorized and X-message-Code = PWD_WRONG [] when triggered from postman, Bruno and other Rest Client.
- ESBMessaging.send role is assigned to the S-user in Subaccount.
- Below error can be seen in Ljs.log of CPI:
09:03:27#+00#ERROR#com.sap.esb.security.cloud.authentication.CloudAuthenticationFilter##anonymous#https-jsse-nio2-8041-exec-1###e1**41d#na#na#na#na#client certificate received at load balancer: none|
2025 06 19 19:03:27#+00#ERROR#com.sap.esb.security.cloud.authentication.CloudAuthenticationFilter##anonymous#https-jsse-nio2-8**1-exec-1###e18**41d#na#na#na#na#client certificate status from load balancer: No Certificate Presented from client side
Read more...
Environment
- SAP Integration Suite
- SAP Business Technology Platform
- NEO Environment
Product
SAP BTP, Neo environment 1.0 ; SAP Integration Suite 1.0
Keywords
Cloud Integration, CPI, Cloud Process Integration, HCI, Basic Authentication, Authorization, Unauthorized, 401, Technical User, Communication User, S-User, Technical Communication User, Integration Flow, iFlow, 401, error code
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.