SAP Community - Cloud Connector

SOAP protocol to Cloud Connector for "Replicate document flow from Business Suite" raises 401 error

2024-03-04T15:52:26.558000+01:00

Hi Community,

by connecting the standard iFlow "Replicate Document Flow from SAP Business Suite" to Cloud Connector with the use of a steady connectivity between SAP BTP, Cloud Foundry runtime and environment and Cloud Connector we have been experiencing a different behaviour as of the IDOC connector, instead. The error raised is:

Error when retrieving external document flow: SoapFaultCode:5 An internal error occurred. For error details check MPL ID AGXl32mXE7Tv2rQGJt2HisYo92XK in message monitoring or use the URL https://<IntegrationSuiteID>.integrationsuite.cfapps.eu10-003.hana.ondemand.com:443/shell/monitoring/MessageDetails/

In fact, with the IDOC connector there is no need of Authentication (Authentication is set to NONE) and the proxy on Cloud Connector acts as expected while getting request from the BTP iFlow request to connect to SAP ERP endpoint (e.g. for "Replicate Business Partner Contact Address to SAP ERP").

Could you please advise on how to achieve the same behaviour with the SOAP protocol?

Best Regards

SAP DM error : ERROR_USER_IS_NOT_AUTHORIZED_IN_CLOUD_CONNECTOR

2024-03-05T13:33:53.980000+01:00

After the last SAP DM release, I got this error message while trying to read indicators through production process design:

However, the user that runs the production process is maintained in the production connector user configuration tab and has all roles as follow:

I checked the cloud connector logs and I found this messages :

Principal propagation subject pattern in cloud connector is maintained as follow :

Error "OData Server return 401 - Unauthorized error" / Browser is not configured to using SPNego

2024-03-06T10:15:30.596000+01:00

Dear Experts,

Could you please help/support on the below error. Recently we have been facing an issue when accessing the SAP Hybrid App in IPAD, After the successful authentication when the call goes to gateway system we are getting this error. More details on the error

Error "Retrieve metadata failed - OData Server return 401 - Unauthorized error" /

Your Browser is not configured to using SPNego

The connections is via SAP BTP and we are seeing the same error logs in cloud platform. But I am not able to see any logs in gateways system.

Kindly let me know or help me to fix this issue. This is very urgent

HTML5 Application 403 Forbidden error while calling Cloud Connector

2024-03-12T15:54:02.407000+01:00

Hello, I have created an UI5 Fiori Application using BAS in BTP. When i do a prereview of the application i am getting the results correctly. The application is picking up Location Hierarchy and putting it in a tree structure. The location hierarchy is read from the On-Premises S4Hana system using Cloud connector and Destination defined in the BTP. In the BAS when i run the CURL command and provide the URL. I am able to get the metadata.

Here is the preview of my application

Now i deployed this application to BTP Cloud Foundry as an HTML5 Application and it was deployed successfully without any error from BAS

Now, when i try to run the application from HTML5 Application Tab/ Repository. I am not able to get the Location tree loaded.

When i debug the calls in Google Chrome developer mode. I noticed there is an 403 Error.

In the Preview tab i see

I spoke to my Network and BASIS Admin. They do not have the UCON enabled in the On-Premises system.

I am totally lost and would appreciate if anyone can help me resolve the issue.

Here is how my xs-app.json file looks like

here is xs-security.json file looks like

Thanks for all your help and time in helping me resolve this issue.

Is it possible to integrate Oracle ERP with SAP CPI from that SAP Commerce?

2024-03-12T18:20:52.993000+01:00

We are using the Oracle ERP as backend system and SAP Commerce as E-Commerce platform. Can we use CPI as middle layer to exchange the data from SAP Commerce to Oracle ERP?

If it is possible could you please point me the documentation to do so.

Thank you

Cloud Connector and Backend Trust Store adding X.509 cert

2024-03-14T09:39:49.946000+01:00

Hi to everyone.

Following Configure Trust | SAP Help Portal I could activate

"Backend Trust Store" adding X.509 certificates.

If I create a RFC connection to an On-Premise backend, which is the X.509 certificate I need to export from, I suppose, strustsso2 transaction?

"System PSE" or "SSL Server Standard" or what else?

Thanks a lot.

Mario

unable to configure cloud connector configuration

2024-03-22T12:53:10.092000+01:00

during configure Cloud connector it showing error.

"An authorization problem occurred when downloading the configuration. Check the spelling of the subaccount name, user, and password. See 'Log And Trace Files' and in particular ljs_trace.log for details. Associated entries were logged on or around 2024-03-22 17:17:03,124 +0530. Consult SAP note 2461997 for possible remedies."

SAP Cloud Connector with terraform

2024-03-25T15:16:51.883000+01:00

Hey, i was wondering if anyone new if it was possible to set up SAP Cloud Connector (adding subaccount, mapping..) with terraform (or another iaac) at this point in time? I cant seem to find any information about it.

Thanks in advance! 🙂

Can't read the metadata from S/4HANA Onprem system from Integration Suite

2024-03-26T01:29:28.140000+01:00

Hi All,

I am trying to build an OData API to expose OData service API_SALES_ORDER_SRV on S/4 HANA Onprem system.

My cloud connector has been configured as

saps4dev400.<host>.local:sapmsDEV

I am trying to configure the OData channel to read the data from S4 Onprem system. In Processing tab, I am trying to configure the resource path using "Remote" as the connection source. My data looks like this.

1. Connection source = Remote

2. Address = http://sapeccdev.<host>.local:443//sap/opu/odata/sap/API_SALES_ORDER_SRV/$metadata

3. Proxy Type = On Premise

4. Location = Blank

5. Authentication = Basic

Credential name = 'ABC' (I have created a security material to store user id and password.) I ma getting an error "Failed to connect to system"

It would be great if someone could help me.

Kind Regards

Shantha

cloud connector

2024-03-26T15:21:52.158000+01:00

Hello Experts,

We are using the SAP BAS to create Fiori Apps.

We established the principal propagation setup between SAP BTP and on-premise System through the SAP cloud connector. SAP CC is in DMZ Zone ( here is proxy configured)
In SAP CC are /sap services are released.
But when I try to access the SAP backend system via SAP BAS, this error occurs: "The selected system is returning an authentication error. Please verify the destination configuration"

Cloud Connector logs:

Spoiler

TRACE#io.netty.handler.codec.http.websocketx.WebSocket08FrameDecoder#tunnel-client-23-3# #Decoding WebSocket Frame opCode=2
TRACE#io.netty.handler.codec.http.websocketx.WebSocket08FrameDecoder#tunnel-client-23-3# #Decoding WebSocket Frame length=4309
TRACE#com.sap.core.connectivity.tunnel.core.handlers.MessagePacketHandler#tunnel-client-3333-444-34555#Received message of type 1 (open connection) over tunnel channel [id: 239i2-3, id: 234, L:/111.111.111:1111 - R:/222.222.222:80]; tunnelId: account:///sss023i4i4/local
TRACE#com.sap.core.connectivity.tunnel.core.impl.processing.TunnelSubscribingProcessor#tunnel-client-23-3#0x8207f8e0#Received subscription request for connection id: 233s-344 to tunnel channel id: 344,44,33. Tunnel id: "account:///340i-dfdf3/local"

Spoiler

DEBUG#com.sap.core.connectivity.tunnel.core.Tunnel#tunnel-client-23-3 3444#Subscribed connectionId 2333 to tunnel channel [id: 3444, id: 234, L:/111.111.111:1111 - R:/222.222.222:80] with tunnelId account:///4543545öfdff/local
#TRACE#com.sap.core.connectivity.tunnel.core.Tunnel#tunnel-client-2523.23344#Tunnel [ objectId [com.sap.core.connectivity.tunnel.core.impl.context.TunnelRegistryImpl$LazyTunnel@3444]; clientId [34444]; tunnelId [account:///34444/local]; currentChannel [0]; tunnelChannels [[[id: 3333, id: 234, L:/111.111.111:1111 - R:/222.222.222:80channelSubscriptions [{-3434=[id: 3444, id: 234, L:/111.111.111:1111 - R:/222.222.222:80]}] ]

#TRACE#com.sap.core.connectivity.tunnel.client.sso.SSOClientProcessor#tunnel-client-3-37#09999#Received SSO token "weweeXXXXX" with type "JWT" for principal type "BUSINESS"; connection origin Id "sb-eu10-app-studio!333", type "CF Connectivity Client ID" and name "unknown" from message packet
DEBUG#com.sap.core.connectivity.tunnel.client.sso.SessionInfoStore#tunnel-client-23-3#43434#Generated new session id 444
#TRACE#com.sap.core.connectivity.tunnel.client.sso.SSOClientSessionService#tunnel-client-23-3#3434#Retrieved connection meta info [originId: sb-eu10-app-studio!2333, originName: unknown, originType: CF Connectivity Client ID] for connectionId 3333
#TRACE#com.sap.core.connectivity.tunnel.client.sso.cf.JWTValidator#tunnel-client-23-3#3434#Parsing JWT: sdsdsdsd-----END PUBLIC KEY-----
#DEBUG#com.sap.core.connectivity.tunnel.client.sso.cf.JWTValidator#tunnel-client-23-#3434#Decoded JWT with claims: {"sub":"33434444434","xs.user.attributes":{},"user_name":"user@mail.com","origin":"sap.default","iss":"... ://88033.hana.ondemand. com/ oauth...","xs.system.attributes":{"xs.rolecollections":["Destination Administrator","Subaccount Viewer","Business_Application_Studio_Extension_Deployer","Business_Application_Studio_Developer","Cloud Connector Administrator","Business_Application_Studio_Administrator","Subaccount Administrator","z_business_appl_studio","Connectivity and Destination Administrator"]},"given_name":"user","client_id":"sb-xxxxx!xx|destination-xsappname!ddd","aud":["uaa","openid","xs_account","destination-xsappname!344","sb-444!b7444|destination-xsappname!sdd","destination-xsappname!sdsd.instance","destination-xsappname!

sdd.subaccount"],"ext_attr":{"enhancer":"XSUAA","subaccountid":"ddd","zdn":"ww","serviceinstanceid":"555"},"user_uuid":"333","zid":"222","grant_type":"urn:ietf:params:oauth:grant-type:jwt-bearer","user_id":"333","azp":"sb-clon2333|destination-xsappname!b404","scope":["destination-xsappname!b404.instance.readDestination","destination- xsappname!b333.instance.manageDestination","user_attributes","destination- xsappname!b333.subaccount.manageCertificate","destination- xsappname!b333.instance.manageCertificate","xs_account.access","openid","destination- xsappname!b333.subaccount.readDestination","uaa.user","destination- xsappname!b333.subaccount.readCertificate","destination- xsappname!b333.subaccount.manageDestination","destination- xsappname!b333manageSubaccountTrust","destination-xsappname!b333.readSubaccountTrust","destination-xsappname!mailc.om b404.instance.readCertificate"],"cnf":{"23#3233":"RQ-2323},"exp":2323,"family_name":"user","iat":222,"jti":"333","email":"user@.user@mail.com","rev_sig":"333","cid":"sb-wewe!wewe|destination-xsappname!b404"}
#com.sap.core.connectivity.tunnel.client.sso.cf.JWTValidator#tunnel-client-25-7#sdsdsd#About to validate token expiration claims [exp, iat] for account dsdsd
DEBUG#com.sap.core.connectivity.tunnel.client.sso.cf.JWTValidator#tunnel-client-25-7#777#Successfully validated token expiration claims [exp, iat] for account 34234
TRACE#com.sap.core.connectivity.tunnel.client.sso.cf.JWTValidator#tunnel-client-25-7#234234#Extracting caller principal name for principal of type BUSINESS
DEBUG#com.sap.core.connectivity.tunnel.client.sso.cf.JWTValidator#tunnel-client-25-wewqe#Caller principal name user@mail.com' was extracted from 'user_name' claim.
DEBUG#com.sap.core.connectivity.tunnel.client.sso.cf.JWTValidator#tunnel-client-25-7#dddf#Successfully validated JWT for tunnelId: account:///asdsad/local
DEBUG#com.sap.core.connectivity.tunnel.client.sso.SessionInfoStore#tunnel-client-7777-fdsf#Stored session with id 2333333
#DEBUG#com.sap.core.connectivity.tunnel.client.sso.CallerPrincipalProviderImpl#tunnel-client-25-7#sdsdssigned principal: 'user@mail.com'
DEBUG#com.sap.core.connectivity.tunnel.core.impl.context.OutboundProtocolProcessorRegistry#tunnel-client-2sd#sdsd#Fallback to default factory for protocol HTTP
DEBUG#com.sap.core.connectivity.tunnel.core.impl.context.OutboundProtocolProcessorRegistry#tunnel-client-25-7#0x8207f8e0#Acquiring outbound connection processor for protocol HTTP
DEBUG#com.sap.core.connectivity.protocol.http.HttpOutboundConnectionProcessorFactory#tunnel-client-25-7#0x8207f8e0#Creating outbound protocol processor for protocol HTTP
#TRACE#io.netty.handler.codec.http.websocketx.WebSocket08FrameDecoder#tunnel-client-23.3# #Decoding WebSocket Frame opCode=2
#TRACE#io.netty.handler.codec.http.websocketx.WebSocket08FrameDecoder#tunnel-client-237# #Decoding WebSocket Frame length=6131
#TRACE#com.sap.core.connectivity.tunnel.core.handlers.MessagePacketHandler#tunnel-client-25-7#0x8207f8e0#Received message of type 3 (payload) with size 6117 over tunnel channel [id: 0x6538d4ba, L:/111.111.111:3345 - R:/111.111.111.:80]; tunnelId: account:///323ddddd/local
#DEBUG#com.sap.core.connectivity.protocol.http.HttpProtocolProcessor#tunnel-client-25-7#99999#Opening connection to backend system test:1213
#TRACE#com.sap.core.connectivity.spi.processing.AbstractProtocolProcessingChannelInitializer#tunnel-client-25-7# #Adding SSL handler for channel: [id: 2323]
#DEBUG#com.sap.scc.security#tunnel-client-23# #Generating X.509 certificate for authentication to backend
#DEBUG#com.sap.scc.security#tunnel-client-23# #Requesting token for principal with name user@mail.com
#DEBUG#com.sap.scc.security#tunnel-client-23# #Extracted attribute from principal ‚user@mail.com‘ with name login_name: null
DEBUG#com.sap.scc.security#tunnel-client-23# #Condition "login_name EXIST" does not fit to principal ‚ user@mail.com‘ , checking next one
#DEBUG#com.sap.scc.security#tunnel-client-25-7# #Extracted attribute from principal ‚user@mail.com‘with name name: null
#com.sap.scc.security#tunnel-client-25-7# #Condition "name EXIST" does not fit to principal user@mail.com, checking next one
#DEBUG#com.sap.scc.security#tunnel-client-25-7# #Condition "true" fits to principal user@mail.com, return CN=${email},
DEBUG#com.sap.scc.security#tunnel-client-25-7# #Generated X.509 certificate with subject CN= user@mail.com,C=DE
#TRACE#com.sap.core.connectivity.spi.processing.AbstractProtocolProcessor#tunnel-client-23#dsd#Connection opening in progress, buffering...
#TRACE#com.sap.core.connectivity.tunnel.core.impl.processing.OutboundPacketProcessor#tunnel-client-23# #Sent packet with size 6,117 to processor com.sap.core.connectivity.protocol.http.HttpProtocolProcessor@23233

#DEBUG#com.sap.core.connectivity.spi.processing.AbstractProtocolProcessor#tunnel-client-25-7#0x8207f8e0#Successfully opened backend connection [id: 0xa026c4cf, L:/111.111.111.111:2334 - R:hostname/111.111.11.111:773]
TRACE#com.sap.core.connectivity.protocol.http.HttpProtocolProcessor#tunnel-client-444#03444e0#Report open connection 774 to http://test:1213
#TRACE#com.sap.core.connectivity.spi.processing.AbstractProtocolProcessor#tunnel-client-23#774#Will send packet with size 6,117 to backend channel [id: 333, L:/ L:/111.111.111.111:2334- R:hostname/111.111.111:3333]
#DEBUG#com.sap.core.connectivity.protocol.http.handlers.HttpRequestStateHandler#tunnel-client-23#344#Starting, switching state to PROCESSING
#DEBUG#com.sap.core.connectivity.protocol.http.handlers.HttpRequestStateHandler#tunnel-client-23#34344#Start sending http://test:1213/sap/opu/odata/IWFND/CATALOGSERVICE;v=2/ServiceCollection/?$top=1&saml2=disabled to backend
#TRACE#com.sap.core.connectivity.protocol.http.handlers.HttpRequestStateHandler#tunnel-client-223#233#Set autoread=FALSE on Backend channel: [id: 3333 isOpen: true; isActive: true; isRegistered: true; isWritable: true; bytesBeforeWritable: 0; bytesBeforeUnwritable: 44,444; autoRead: false]
#TRACE#com.sap.core.connectivity.protocol.http.handlers.HttpInboundStatisticsHandler#tunnel-client-23-7#3333#Set request description to statistics instance: http://test:1213/sap/opu/odata/IWFND/CATALOGSERVICE;v=2/ServiceCollection/?$top=1&saml2=disabled on [virtualHost=test, virtualPort=1213, protocol=HTTP]
#TRACE#com.sap.core.connectivity.protocol.http.handlers.HttpInboundStatisticsHandler#tunnel-client-23#233#Report invoke started for connection 0x8207f8e0 to http://test:1213 request /sap/opu/odata/IWFND/CATALOGSERVICE;v=2/ServiceCollection/
#DEBUG#com.sap.core.connectivity.protocol.http.handlers.HttpAuthenticationHandler#tunnel-client-3#0x8207f8e0#Updating caller principal.
#DEBUG#com.sap.core.connectivity.tunnel.client.sso.SSOClientSessionService#tunnel-client-23# #Reusing existing session with id 2333
#DEBUG#com.sap.core.connectivity.tunnel.client.sso.CallerPrincipalProviderImpl#tunnel-client-25-7# #Assigned principal: 'user@mail.com'
DEBUG#com.sap.core.connectivity.protocol.http.handlers.HttpAuthenticationHandler#tunnel-client-25-7#0x8207f8e0#Will use X.509 certificate for authentication to backend: 2333333(SHA-256)
#DEBUG#com.sap.core.connectivity.protocol.http.handlers.HttpAuthorizationHandler#tunnel-client-25-7#34344#Access allowed to http://test:1213/sap/opu/odata/IWFND/CATALOGSERVICE;v=2/ServiceCollection/?$top=1&saml2=disabled for virtual host test:1213
#DEBUG#com.sap.core.connectivity.protocol.http.handlers.HttpRequestStateHandler#tunnel-client-25-7#3444#Last http request object, switching state to SWALLOWING
#TRACE#com.sap.core.connectivity.protocol.http.handlers.HttpRequestStateHandler#tunnel-client-23#344#Set autoread=TRUE on Backend channel: [id: 0xa026c4cf isOpen: true; isActive: true; isRegistered: true; isWritable: true; bytesBeforeWritable: 0; bytesBeforeUnwritable: 4,444; autoRead: true]
#DEBUG#com.sap.core.connectivity.protocol.http.handlers.HttpResponseStateHandler#tunnel-client-343444#Last http request object, switching state to STARTING
#DEBUG#io.netty.handler.ssl.SslHandler#tunnel-client-23# #[id: 333, L:/111.111.111.:3333 - R:hostname.com/111.111.111:2333] HANDSHAKEN: protocol:TLSv1.2 cipher suite:TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
TRACE#com.sap.core.connectivity.spi.processing.AbstractProtocolProcessor#tunnel-client-23#233#Sent packet with size 3 to backend channel [id: 233, L:/111.111.111:3333- R:hostname.com/111.111.111.46667]
#DEBUG#com.sap.core.connectivity.protocol.http.handlers.HttpResponseStateHandler#tunnel-client-23eeee#Starting, switching state to PROCESSING
#DEBUG#com.sap.core.connectivity.protocol.http.handlers.HttpSapStatisticsHandler#tunnel-client-33-7#333#Performance statistics is disabled,sap-statistics-scc header is not set
#TRACE#com.sap.core.connectivity.tunnel.core.Tunnel#tunnel-client-25-7# #Will send message of type 3 (payload) with size 328 over tunnel channel [id: 333, L:/111.111.111:3333 - R:/111.111.111:80] with tunnelId account:///34444/local
TRACE#io.netty.handler.codec.http.websocketx.WebSocket08FrameEncoder#tunnel-client-23# #Encoding WebSocket Frame opCode=2 length=342
#TRACE#com.sap.core.connectivity.tunnel.core.Tunnel#tunnel-client-23# #Sent message of type 3 (payload) with payload size 328 over tunnel channel [id: 0x6538d4ba, L:/111.111.111:3444 - R:/111.111.111:80] with tunnelId account:///33444444/local

com.sap.core.connectivity.spi.processing.OutboundConnectionReader#tunnel-client-2344#Sent message of type 3 (payload) with payload size 328 to tunnel channel [id: 344, L:/111.111.111:3444 - R:/111.111.111:80]
#DEBUG#com.sap.core.connectivity.protocol.http.handlers.HttpResponseStateHandler#tunnel-client-23#wewe#Last http response object, switching state to SWALLOWING
#DEBUG#com.sap.core.connectivity.protocol.http.handlers.HttpRequestStateHandler#tunnel-client-25-7#344#Last http response object, switching state to STARTING
#TRACE#com.sap.core.connectivity.tunnel.core.Tunnel#tunnel-client-23# #Will send message of type 3 (payload) with size 6612 over tunnel channel [id: 0x6538d4ba, L:/111.111.111:3444 - R:/111.111.111:80]] with tunnelId account://wewewe/local
TRACE#io.netty.handler.codec.http.websocketx.WebSocket08FrameEncoder#tunnel-client-25-7# #Encoding WebSocket Frame opCode=2 length=6626
#TRACE#com.sap.core.connectivity.tunnel.core.Tunnel#tunnel-client-25-7# #Sent message of type 3 (payload) with payload size 6612 over tunnel channel [id: 23423, L:/111.111.111:3444 - R:/111.111.111:80]] with tunnelId account:///11111/local
#TRACE#com.sap.core.connectivity.spi.processing.OutboundConnectionReader#tunnel-client-23233#Sent message of type 3 (payload) with payload size 6,612 to tunnel channel [id: 2323, L:/111.111.111:3444 - R:/111.111.111:80]]
TRACE#com.sap.core.connectivity.protocol.http.handlers.HttpInboundStatisticsHandler#tunnel-client-23333#Report http request on connection 3444 to http://test:1213 request /sap/opu/odata/IWFND/CATALOGSERVICE;v=2/ServiceCollection/
#TRACE#com.sap.core.connectivity.protocol.http.handlers.HttpInboundStatisticsHandler#tunnel-client-34#0x8207f8e0#Report http request time statistics: total=73,ext=34,latency=3,openRemoteConn=28,generateSSOToken=24,validateSSOToken=0
#TRACE#com.sap.scc.monitor#tunnel-client-25-7# #Request HTTP://test:1213 resource /sap/opu/odata/IWFND/CATALOGSERVICE;v=2/ServiceCollection/ with total time 73 is added to top list.
#TRACE#com.sap.scc.monitor#tunnel-client-25-7# #Request HTTP://test:1213 resource /sap/opu/odata/IWFND/CATALOGSERVICE;v=2/ServiceCollection/ with total time 73 is added to top list.
#DEBUG#com.sap.core.connectivity.spi.processing.OutboundConnectionErrorHandler#tunnel-client-25-7#weee#Backend channel [id: weee L:/111.111.111:3444 - R:/111.111.111:80] is closed
#TRACE#com.sap.core.connectivity.tunnel.core.Tunnel#tunnel-client-23# #Will send message of type 4 (error) over tunnel channel [id: wewe, L:/111.111.111:3444 - R:/111.111.111:80]] with tunnelId account:///223/local
TRACE#io.netty.handler.codec.http.websocketx.WebSocket08FrameEncoder#tunnel-client-23# #Encoding WebSocket Frame opCode=2 length=231
#TRACE#com.sap.core.connectivity.tunnel.core.Tunnel#tunnel-client-23# #Sent message of type 4 (error) over tunnel channel [id: 0x6538d4ba, L:/111.111.111:3444 - R:/111.111.111:80]] with tunnelId account:///w343434/local
#TRACE#io.netty.handler.codec.http.websocketx.WebSocket08FrameDecoder#tunnel-client-23# #Decoding WebSocket Frame opCode=2
#TRACE#io.netty.handler.codec.http.websocketx.WebSocket08FrameDecoder#tunnel-client-23# #Decoding WebSocket Frame length=14
#TRACE#com.sap.core.connectivity.tunnel.core.handlers.MessagePacketHandler#tunnel-client-23-wewe#Received message of type 2 (close connection) over tunnel channel [id: 2434, L:/111.111.111:3444 - R:/111.111.111:80]]; tunnelId: account:///wewewe 2/local
DEBUG#com.sap.core.connectivity.tunnel.core.Tunnel#tunnel-client-25-7#0x8207f8e0#Unsubscribed connectionId 0x8207f8e0 from tunnelId account:///ewewe2/local
#DEBUG#com.sap.core.connectivity.tunnel.client.sso.CallerPrincipalProviderImpl#tunnel-client-25-7#33434#Unassigned principal: user@mail.com
#DEBUG#com.sap.core.connectivity.spi.processing.AbstractProtocolProcessor#tunnel-client-23#Released backend connection channel [id: 233, L:/1111.111.111:5554 ! R:hostname.com/3111.111.111:3333]

R:hostname.com/3111.111.111:3333]
TRACE#com.sap.core.connectivity.protocol.http.HttpProtocolProcessor#tunnel-client-24#Report close connection with id: 444
#TRACE#io.netty.handler.codec.http.websocketx.WebSocket08FrameDecoder#notification-client-24-1# #Decoding WebSocket Frame opCode=10
+0100#TRACE#com.sap.core.connectivity.tunnel.core.handlers.TunnelStateHandler#notification-client-24-1# #Received pong for channel [id: erer, L:/111.111.111:3434 - R:/111.111.111:80] with tunnelId account:///232333
#TRACE#com.sap.core.connectivity.tunnel.core.handlers.TunnelStateHandler#notification-client-223# #Sending pong for channel [id: 333, L:/111.111.111:344 - R:/111.111.111:80] with tunnelId account:///23233
TRACE#com.sap.core.connectivity.tunnel.core.handlers.TunnelStateHandler#notification-client-21-1# #Sending pong for channel [id: 3434, L:/111.111.111:344 - R:/111.111.111:80] with tunnelId account:///67777/local
#TRACE#io.netty.handler.codec.http.websocketx.WebSocket08FrameEncoder#notification-client-21-1# #Encoding WebSocket Frame opCode=10 length=0
#TRACE#com.sap.core.connectivity.tunnel.core.handlers.TunnelStateHandler#notification-client-21-1# #Received pong for channel [id: wee, , L:/111.111.111:344 - R:/111.111.111:80] with tunnelId account:///wee2/local
#TRACE#com.sap.core.connectivity.tunnel.core.handlers.TunnelStateHandler#tunnel-client-3# #Sending pong for channel [id: 0x6538d4ba, L:/111.111.111:344 - R:/111.111.111:80] with tunnelId account:///wee2/local sdsdsd:06:01,740
#io.netty.handler.codec.http.websocketx.WebSocket08FrameEncoder#tunnel-client-23# #Encoding WebSocket Frame opCode=10 length=0
#TRACE#com.sap.scc.ui#https-jsse-nio2-43311-exec-9# #execute incoming request /configuration with action 'getAccounts'
0#TRACE#com.sap.scc.ui#https-jsse-nio2-43311-exec-9# #incoming request /configuration action: getAccounts finished after 0 ms
0#TRACE#com.sap.scc.ui#https-jsse-nio2-43311-exec-2# #execute incoming request /admin with action 'fetchMessages'
TRACE#com.sap.scc.ui#https-jsse-nio2-43311-exec-2# #incoming request /admin action: fetchMessages finished after 1 ms
TRACE#com.sap.scc.ui#https-jsse-nio2-43311-exec-6# #execute incoming request /logAndTrace with action 'getLogSettings'
#TRACE#com.sap.scc.ui#https-jsse-nio2-43311-exec-6# #incoming request /logAndTrace action: getLogSettings finished after 1 ms
#TRACE#com.sap.scc.ui#https-jsse-nio2-43311-exec-10# #execute incoming request /logAndTrace with action 'getLogFiles'

com.sap.core.connectivity.tunnel.client.handshake.AbstractClientHandshaker#tunnel-client-25-7# #Handshake with tunnel server completed successfully for tunnelId: account:///sdd/localcom.sap.core.connectivity.tunnel.core.impl.context.TunnelRegistryImpl#tunnel-client-44 #Registered tunnel channel [id: 234, L:/111.111.111:1111 - R:/222.222.222:80] for tunnelId account:///2kdkd-2/local and client Id 4dfjfffINFO#com.sap.core.connectivity.tunnel.client.TunnelClient#tunnel-client-22# #Successfully established tunnel channel: [id: 234, L:/111.111.111:1111 - R:/222.222.222:80]DEBUG#io.netty.channel.DefaultChannelPipeline#tunnel-client-23# #Discarded inbound message EmptyLastHttpContent that reached at the tail of the pipeline. Please check your pipeline configuration.DEBUG#io.netty.channel.DefaultChannelPipeline#tunnel-client-25-7# #Discarded message pipeline : [idleStateHandler, ssl, wsencoder, wsdecoder, tunnelStateHandler, protocolEncoder, protocolDecoder, payloadTracer, flowControlHandler, messagePacketHandler, tunnelErrorHandler, DefaultChannelPipeline$TailContext#0]. Channel : id: 234, L:/111.111.111:1111 - R:/222.222.222:80TRACE#io.netty.handler.codec.http.websocketx.WebSocket08FrameDecoder#tunnel-client-23-3# #Decoding WebSocket Frame opCode=2TRACE#io.netty.handler.codec.http.websocketx.WebSocket08FrameDecoder#tunnel-client-23-3# #Decoding WebSocket Frame length=4309TRACE#com.sap.core.connectivity.tunnel.core.handlers.MessagePacketHandler#tunnel-client-3333-444-34555#Received message of type 1 (open connection) over tunnel channel [id: 239i2-3, id: 234, L:/111.111.111:1111 - R:/222.222.222:80]; tunnelId: account:///sss023i4i4/localTRACE#com.sap.core.connectivity.tunnel.core.impl.processing.TunnelSubscribingProcessor#tunnel-client-23-3#0x8207f8e0#Received subscription request for connection id: 233s-344 to tunnel channel id: 344,44,33. Tunnel id: "account:///340i-dfdf3/local"DEBUG#com.sap.core.connectivity.tunnel.core.Tunnel#tunnel-client-23-3 3444#Subscribed connectionId 2333 to tunnel channel [id: 3444, id: 234, L:/111.111.111:1111 - R:/222.222.222:80] with tunnelId account:///4543545öfdff/local#TRACE#com.sap.core.connectivity.tunnel.core.Tunnel#tunnel-client-2523.23344#Tunnel [ objectId [com.sap.core.connectivity.tunnel.core.impl.context.TunnelRegistryImpl$LazyTunnel@3444]; clientId [34444]; tunnelId [account:///34444/local]; currentChannel [0]; tunnelChannels [[[id: 3333, id: 234, L:/111.111.111:1111 - R:/222.222.222:80channelSubscriptions [{-3434=[id: 3444, id: 234, L:/111.111.111:1111 - R:/222.222.222:80]}] ]#TRACE#com.sap.core.connectivity.tunnel.client.sso.SSOClientProcessor#tunnel-client-3-37#09999#Received SSO token "weweeXXXXX" with type "JWT" for principal type "BUSINESS"; connection origin Id "sb-eu10-app-studio!333", type "CF Connectivity Client ID" and name "unknown" from message packetDEBUG#com.sap.core.connectivity.tunnel.client.sso.SessionInfoStore#tunnel-client-23-3#43434#Generated new session id 444#TRACE#com.sap.core.connectivity.tunnel.client.sso.SSOClientSessionService#tunnel-client-23-3#3434#Retrieved connection meta info [originId: sb-eu10-app-studio!2333, originName: unknown, originType: CF Connectivity Client ID] for connectionId 3333#TRACE#com.sap.core.connectivity.tunnel.client.sso.cf.JWTValidator#tunnel-client-23-3#3434#Parsing JWT: sdsdsdsd-----END PUBLIC KEY-----#DEBUG#com.sap.core.connectivity.tunnel.client.sso.cf.JWTValidator#tunnel-client-23-#3434#Decoded JWT with claims: {"sub":"33434444434","xs.user.attributes":{},"user_name":"user@mail.com","origin":"sap.default","iss":"... ://88033.hana.ondemand. com/ oauth...","xs.system.attributes":{"xs.rolecollections":["Destination Administrator","Subaccount Viewer","Business_Application_Studio_Extension_Deployer","Business_Application_Studio_Developer","Cloud Connector Administrator","Business_Application_Studio_Administrator","Subaccount Administrator","z_business_appl_studio","Connectivity and Destination Administrator"]},"given_name":"user","client_id":"sb-xxxxx!xx|destination-xsappname!ddd","aud":["uaa","openid","xs_account","destination-xsappname!344","sb-444!b7444|destination-xsappname!sdd","destination-xsappname!sdsd.instance","destination-xsappname!sdd.subaccount"],"ext_attr":{"enhancer":"XSUAA","subaccountid":"ddd","zdn":"ww","serviceinstanceid":"555"},"user_uuid":"333","zid":"222","grant_type":"urn:ietf:params:oauth:grant-type:jwt-bearer","user_id":"333","azp":"sb-clon2333|destination-xsappname!b404","scope":["destination-xsappname!b404.instance.readDestination","destination- xsappname!b333.instance.manageDestination","user_attributes","destination- xsappname!b333.subaccount.manageCertificate","destination- xsappname!b333.instance.manageCertificate","xs_account.access","openid","destination- xsappname!b333.subaccount.readDestination","uaa.user","destination- xsappname!b333.subaccount.readCertificate","destination- xsappname!b333.subaccount.manageDestination","destination- xsappname!b333manageSubaccountTrust","destination-xsappname!b333.readSubaccountTrust","destination-xsappname!mailc.om b404.instance.readCertificate"],"cnf":{"23#3233":"RQ-2323},"exp":2323,"family_name":"user","iat":222,"jti":"333","email":"user@.user@mail.com","rev_sig":"333","cid":"sb-wewe!wewe|destination-xsappname!b404"}#com.sap.core.connectivity.tunnel.client.sso.cf.JWTValidator#tunnel-client-25-7#sdsdsd#About to validate token expiration claims [exp, iat] for account dsdsdDEBUG#com.sap.core.connectivity.tunnel.client.sso.cf.JWTValidator#tunnel-client-25-7#777#Successfully validated token expiration claims [exp, iat] for account 34234TRACE#com.sap.core.connectivity.tunnel.client.sso.cf.JWTValidator#tunnel-client-25-7#234234#Extracting caller principal name for principal of type BUSINESSDEBUG#com.sap.core.connectivity.tunnel.client.sso.cf.JWTValidator#tunnel-client-25-wewqe#Caller principal name user@mail.com' was extracted from 'user_name' claim.DEBUG#com.sap.core.connectivity.tunnel.client.sso.cf.JWTValidator#tunnel-client-25-7#dddf#Successfully validated JWT for tunnelId: account:///asdsad/localDEBUG#com.sap.core.connectivity.tunnel.client.sso.SessionInfoStore#tunnel-client-7777-fdsf#Stored session with id 2333333#DEBUG#com.sap.core.connectivity.tunnel.client.sso.CallerPrincipalProviderImpl#tunnel-client-25-7#sdsdssigned principal: 'user@mail.com'DEBUG#com.sap.core.connectivity.tunnel.core.impl.context.OutboundProtocolProcessorRegistry#tunnel-client-2sd#sdsd#Fallback to default factory for protocol HTTPDEBUG#com.sap.core.connectivity.tunnel.core.impl.context.OutboundProtocolProcessorRegistry#tunnel-client-25-7#0x8207f8e0#Acquiring outbound connection processor for protocol HTTPDEBUG#com.sap.core.connectivity.protocol.http.HttpOutboundConnectionProcessorFactory#tunnel-client-25-7#0x8207f8e0#Creating outbound protocol processor for protocol HTTP#TRACE#io.netty.handler.codec.http.websocketx.WebSocket08FrameDecoder#tunnel-client-23.3# #Decoding WebSocket Frame opCode=2#TRACE#io.netty.handler.codec.http.websocketx.WebSocket08FrameDecoder#tunnel-client-237# #Decoding WebSocket Frame length=6131#TRACE#com.sap.core.connectivity.tunnel.core.handlers.MessagePacketHandler#tunnel-client-25-7#0x8207f8e0#Received message of type 3 (payload) with size 6117 over tunnel channel [id: 0x6538d4ba, L:/111.111.111:3345 - R:/111.111.111.:80]; tunnelId: account:///323ddddd/local#DEBUG#com.sap.core.connectivity.protocol.http.HttpProtocolProcessor#tunnel-client-25-7#99999#Opening connection to backend system test:1213#TRACE#com.sap.core.connectivity.spi.processing.AbstractProtocolProcessingChannelInitializer#tunnel-client-25-7# #Adding SSL handler for channel: [id: 2323]#DEBUG#com.sap.scc.security#tunnel-client-23# #Generating X.509 certificate for authentication to backend#DEBUG#com.sap.scc.security#tunnel-client-23# #Requesting token for principal with name user@mail.com#DEBUG#com.sap.scc.security#tunnel-client-23# #Extracted attribute from principal ‚user@mail.com‘ with name login_name: nullDEBUG#com.sap.scc.security#tunnel-client-23# #Condition "login_name EXIST" does not fit to principal ‚ user@mail.com‘ , checking next one#DEBUG#com.sap.scc.security#tunnel-client-25-7# #Extracted attribute from principal ‚user@mail.com‘with name name: null#com.sap.scc.security#tunnel-client-25-7# #Condition "name EXIST" does not fit to principal user@mail.com, checking next one#DEBUG#com.sap.scc.security#tunnel-client-25-7# #Condition "true" fits to principal user@mail.com, return CN=${email},DEBUG#com.sap.scc.security#tunnel-client-25-7# #Generated X.509 certificate with subject CN= user@mail.com,C=DE#TRACE#com.sap.core.connectivity.spi.processing.AbstractProtocolProcessor#tunnel-client-23#dsd#Connection opening in progress, buffering...#TRACE#com.sap.core.connectivity.tunnel.core.impl.processing.OutboundPacketProcessor#tunnel-client-23# #Sent packet with size 6,117 to processor com.sap.core.connectivity.protocol.http.HttpProtocolProcessor@23233#DEBUG#com.sap.core.connectivity.spi.processing.AbstractProtocolProcessor#tunnel-client-25-7#0x8207f8e0#Successfully opened backend connection [id: 0xa026c4cf, L:/111.111.111.111:2334 - R:hostname/111.111.11.111:773]TRACE#com.sap.core.connectivity.protocol.http.HttpProtocolProcessor#tunnel-client-444#03444e0#Report open connection 774 to http://test:1213#TRACE#com.sap.core.connectivity.spi.processing.AbstractProtocolProcessor#tunnel-client-23#774#Will send packet with size 6,117 to backend channel [id: 333, L:/ L:/111.111.111.111:2334- R:hostname/111.111.111:3333]#DEBUG#com.sap.core.connectivity.protocol.http.handlers.HttpRequestStateHandler#tunnel-client-23#344#Starting, switching state to PROCESSING#DEBUG#com.sap.core.connectivity.protocol.http.handlers.HttpRequestStateHandler#tunnel-client-23#34344#Start sending http://test:1213/sap/opu/odata/IWFND/CATALOGSERVICE;v=2/ServiceCollection/?$top=1&saml2=disabled to backend#TRACE#com.sap.core.connectivity.protocol.http.handlers.HttpRequestStateHandler#tunnel-client-223#233#Set autoread=FALSE on Backend channel: [id: 3333 isOpen: true; isActive: true; isRegistered: true; isWritable: true; bytesBeforeWritable: 0; bytesBeforeUnwritable: 44,444; autoRead: false]#TRACE#com.sap.core.connectivity.protocol.http.handlers.HttpInboundStatisticsHandler#tunnel-client-23-7#3333#Set request description to statistics instance: http://test:1213/sap/opu/odata/IWFND/CATALOGSERVICE;v=2/ServiceCollection/?$top=1&saml2=disabled on [virtualHost=test, virtualPort=1213, protocol=HTTP]#TRACE#com.sap.core.connectivity.protocol.http.handlers.HttpInboundStatisticsHandler#tunnel-client-23#233#Report invoke started for connection 0x8207f8e0 to http://test:1213 request /sap/opu/odata/IWFND/CATALOGSERVICE;v=2/ServiceCollection/#DEBUG#com.sap.core.connectivity.protocol.http.handlers.HttpAuthenticationHandler#tunnel-client-3#0x8207f8e0#Updating caller principal.#DEBUG#com.sap.core.connectivity.tunnel.client.sso.SSOClientSessionService#tunnel-client-23# #Reusing existing session with id 2333#DEBUG#com.sap.core.connectivity.tunnel.client.sso.CallerPrincipalProviderImpl#tunnel-client-25-7# #Assigned principal: 'user@mail.com'DEBUG#com.sap.core.connectivity.protocol.http.handlers.HttpAuthenticationHandler#tunnel-client-25-7#0x8207f8e0#Will use X.509 certificate for authentication to backend: 2333333(SHA-256)#DEBUG#com.sap.core.connectivity.protocol.http.handlers.HttpAuthorizationHandler#tunnel-client-25-7#34344#Access allowed to http://test:1213/sap/opu/odata/IWFND/CATALOGSERVICE;v=2/ServiceCollection/?$top=1&saml2=disabled for virtual host test:1213#DEBUG#com.sap.core.connectivity.protocol.http.handlers.HttpRequestStateHandler#tunnel-client-25-7#3444#Last http request object, switching state to SWALLOWING#TRACE#com.sap.core.connectivity.protocol.http.handlers.HttpRequestStateHandler#tunnel-client-23#344#Set autoread=TRUE on Backend channel: [id: 0xa026c4cf isOpen: true; isActive: true; isRegistered: true; isWritable: true; bytesBeforeWritable: 0; bytesBeforeUnwritable: 4,444; autoRead: true]#DEBUG#com.sap.core.connectivity.protocol.http.handlers.HttpResponseStateHandler#tunnel-client-343444#Last http request object, switching state to STARTING#DEBUG#io.netty.handler.ssl.SslHandler#tunnel-client-23# #[id: 333, L:/111.111.111.:3333 - R:hostname.com/111.111.111:2333] HANDSHAKEN: protocol:TLSv1.2 cipher suite:TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256TRACE#com.sap.core.connectivity.spi.processing.AbstractProtocolProcessor#tunnel-client-23#233#Sent packet with size 3 to backend channel [id: 233, L:/111.111.111:3333- R:hostname.com/111.111.111.46667]#DEBUG#com.sap.core.connectivity.protocol.http.handlers.HttpResponseStateHandler#tunnel-client-23eeee#Starting, switching state to PROCESSING#DEBUG#com.sap.core.connectivity.protocol.http.handlers.HttpSapStatisticsHandler#tunnel-client-33-7#333#Performance statistics is disabled,sap-statistics-scc header is not set#TRACE#com.sap.core.connectivity.tunnel.core.Tunnel#tunnel-client-25-7# #Will send message of type 3 (payload) with size 328 over tunnel channel [id: 333, L:/111.111.111:3333 - R:/111.111.111:80] with tunnelId account:///34444/localTRACE#io.netty.handler.codec.http.websocketx.WebSocket08FrameEncoder#tunnel-client-23# #Encoding WebSocket Frame opCode=2 length=342#TRACE#com.sap.core.connectivity.tunnel.core.Tunnel#tunnel-client-23# #Sent message of type 3 (payload) with payload size 328 over tunnel channel [id: 0x6538d4ba, L:/111.111.111:3444 - R:/111.111.111:80] with tunnelId account:///33444444/localcom.sap.core.connectivity.spi.processing.OutboundConnectionReader#tunnel-client-2344#Sent message of type 3 (payload) with payload size 328 to tunnel channel [id: 344, L:/111.111.111:3444 - R:/111.111.111:80]#DEBUG#com.sap.core.connectivity.protocol.http.handlers.HttpResponseStateHandler#tunnel-client-23#wewe#Last http response object, switching state to SWALLOWING#DEBUG#com.sap.core.connectivity.protocol.http.handlers.HttpRequestStateHandler#tunnel-client-25-7#344#Last http response object, switching state to STARTING#TRACE#com.sap.core.connectivity.tunnel.core.Tunnel#tunnel-client-23# #Will send message of type 3 (payload) with size 6612 over tunnel channel [id: 0x6538d4ba, L:/111.111.111:3444 - R:/111.111.111:80]] with tunnelId account://wewewe/localTRACE#io.netty.handler.codec.http.websocketx.WebSocket08FrameEncoder#tunnel-client-25-7# #Encoding WebSocket Frame opCode=2 length=6626#TRACE#com.sap.core.connectivity.tunnel.core.Tunnel#tunnel-client-25-7# #Sent message of type 3 (payload) with payload size 6612 over tunnel channel [id: 23423, L:/111.111.111:3444 - R:/111.111.111:80]] with tunnelId account:///11111/local#TRACE#com.sap.core.connectivity.spi.processing.OutboundConnectionReader#tunnel-client-23233#Sent message of type 3 (payload) with payload size 6,612 to tunnel channel [id: 2323, L:/111.111.111:3444 - R:/111.111.111:80]]TRACE#com.sap.core.connectivity.protocol.http.handlers.HttpInboundStatisticsHandler#tunnel-client-23333#Report http request on connection 3444 to http://test:1213 request /sap/opu/odata/IWFND/CATALOGSERVICE;v=2/ServiceCollection/#TRACE#com.sap.core.connectivity.protocol.http.handlers.HttpInboundStatisticsHandler#tunnel-client-34#0x8207f8e0#Report http request time statistics: total=73,ext=34,latency=3,openRemoteConn=28,generateSSOToken=24,validateSSOToken=0#TRACE#com.sap.scc.monitor#tunnel-client-25-7# #Request HTTP://test:1213 resource /sap/opu/odata/IWFND/CATALOGSERVICE;v=2/ServiceCollection/ with total time 73 is added to top list.#TRACE#com.sap.scc.monitor#tunnel-client-25-7# #Request HTTP://test:1213 resource /sap/opu/odata/IWFND/CATALOGSERVICE;v=2/ServiceCollection/ with total time 73 is added to top list.#DEBUG#com.sap.core.connectivity.spi.processing.OutboundConnectionErrorHandler#tunnel-client-25-7#weee#Backend channel [id: weee L:/111.111.111:3444 - R:/111.111.111:80] is closed#TRACE#com.sap.core.connectivity.tunnel.core.Tunnel#tunnel-client-23# #Will send message of type 4 (error) over tunnel channel [id: wewe, L:/111.111.111:3444 - R:/111.111.111:80]] with tunnelId account:///223/localTRACE#io.netty.handler.codec.http.websocketx.WebSocket08FrameEncoder#tunnel-client-23# #Encoding WebSocket Frame opCode=2 length=231#TRACE#com.sap.core.connectivity.tunnel.core.Tunnel#tunnel-client-23# #Sent message of type 4 (error) over tunnel channel [id: 0x6538d4ba, L:/111.111.111:3444 - R:/111.111.111:80]] with tunnelId account:///w343434/local#TRACE#io.netty.handler.codec.http.websocketx.WebSocket08FrameDecoder#tunnel-client-23# #Decoding WebSocket Frame opCode=2#TRACE#io.netty.handler.codec.http.websocketx.WebSocket08FrameDecoder#tunnel-client-23# #Decoding WebSocket Frame length=14#TRACE#com.sap.core.connectivity.tunnel.core.handlers.MessagePacketHandler#tunnel-client-23-wewe#Received message of type 2 (close connection) over tunnel channel [id: 2434, L:/111.111.111:3444 - R:/111.111.111:80]]; tunnelId: account:///wewewe 2/localDEBUG#com.sap.core.connectivity.tunnel.core.Tunnel#tunnel-client-25-7#0x8207f8e0#Unsubscribed connectionId 0x8207f8e0 from tunnelId account:///ewewe2/local#DEBUG#com.sap.core.connectivity.tunnel.client.sso.CallerPrincipalProviderImpl#tunnel-client-25-7#33434#Unassigned principal: user@mail.com#DEBUG#com.sap.core.connectivity.spi.processing.AbstractProtocolProcessor#tunnel-client-23#Released backend connection channel [id: 233, L:/1111.111.111:5554 ! R:hostname.com/3111.111.111:3333]R:hostname.com/3111.111.111:3333]TRACE#com.sap.core.connectivity.protocol.http.HttpProtocolProcessor#tunnel-client-24#Report close connection with id: 444#TRACE#io.netty.handler.codec.http.websocketx.WebSocket08FrameDecoder#notification-client-24-1# #Decoding WebSocket Frame opCode=10+0100#TRACE#com.sap.core.connectivity.tunnel.core.handlers.TunnelStateHandler#notification-client-24-1# #Received pong for channel [id: erer, L:/111.111.111:3434 - R:/111.111.111:80] with tunnelId account:///232333#TRACE#com.sap.core.connectivity.tunnel.core.handlers.TunnelStateHandler#notification-client-223# #Sending pong for channel [id: 333, L:/111.111.111:344 - R:/111.111.111:80] with tunnelId account:///23233TRACE#com.sap.core.connectivity.tunnel.core.handlers.TunnelStateHandler#notification-client-21-1# #Sending pong for channel [id: 3434, L:/111.111.111:344 - R:/111.111.111:80] with tunnelId account:///67777/local#TRACE#io.netty.handler.codec.http.websocketx.WebSocket08FrameEncoder#notification-client-21-1# #Encoding WebSocket Frame opCode=10 length=0#TRACE#com.sap.core.connectivity.tunnel.core.handlers.TunnelStateHandler#notification-client-21-1# #Received pong for channel [id: wee, , L:/111.111.111:344 - R:/111.111.111:80] with tunnelId account:///wee2/local#TRACE#com.sap.core.connectivity.tunnel.core.handlers.TunnelStateHandler#tunnel-client-3# #Sending pong for channel [id: 0x6538d4ba, L:/111.111.111:344 - R:/111.111.111:80] with tunnelId account:///wee2/local sdsdsd:06:01,740#io.netty.handler.codec.http.websocketx.WebSocket08FrameEncoder#tunnel-client-23# #Encoding WebSocket Frame opCode=10 length=0#TRACE#com.sap.scc.ui#https-jsse-nio2-43311-exec-9# #execute incoming request /configuration with action 'getAccounts'0#TRACE#com.sap.scc.ui#https-jsse-nio2-43311-exec-9# #incoming request /configuration action: getAccounts finished after 0 ms0#TRACE#com.sap.scc.ui#https-jsse-nio2-43311-exec-2# #execute incoming request /admin with action 'fetchMessages'TRACE#com.sap.scc.ui#https-jsse-nio2-43311-exec-2# #incoming request /admin action: fetchMessages finished after 1 msTRACE#com.sap.scc.ui#https-jsse-nio2-43311-exec-6# #execute incoming request /logAndTrace with action 'getLogSettings'#TRACE#com.sap.scc.ui#https-jsse-nio2-43311-exec-6# #incoming request /logAndTrace action: getLogSettings finished after 1 ms#TRACE#com.sap.scc.ui#https-jsse-nio2-43311-exec-10# #execute incoming request /logAndTrace with action 'getLogFiles'

Spoiler

Could you please help up with this problem.

Thanks.

Restrict some IP (BTP data center IP) for Outbound Call from SAP Integration Suite

2024-04-02T06:38:17.198000+02:00

Hello,

This is the 2nd time I have encountered the same problem where receiving party is saying that they can whitelist up-to 6 IPs only. We are having SAP Integration Suite as middle ware where some data is being send from SAP to Receiving party via API/SFTP.

I have asked the same to SAP but as per them it is not possible to restrict IPs for outbound connection. Some time receiving party adjust and whitelist all the IPs but in case of they simply denied and we don't have any solution.

For the solution I have come across where as per the SAP note we can minimize the IP via cloud connector but not able to find how to do that. Can someone guide on this topic.

reference screenshot from SAP note : 3209308

Thanks,

Aman Sharma

AWS Postgres sql via cloud connector - unable to connect using socket

2024-04-02T09:51:05.675000+02:00

Hi ,

I have a Postgres DB instance from AWS. The host is not exposed to public internet access, hence a cloud foundry instance does not have direct access . But my cloud foundry instance has access to it. I added a TCP connection - Connectivity check passes ( telnet successfully connects to 5432 port of this host , from OS level )

Now, following similar questions and git repo by piejanssens , I set up the codebase for it.
code and log is uploaded here

error thrown "

OUT Socket error: Error: getaddrinfo ENOTFOUND aws-rds-dev

" , though the authentication is successful .

@gregorw Have you tried this already ?

Retrieve metadata failed because the OData server returned HTTP code, 401

2024-04-04T13:08:28.401000+02:00

Dear Experts,

Error Retrieve metadata failed because the OData server returned HTTP code, 401 with message "Logon Error Message"

The connections is via SAP BTP and we are seeing the same error logs in cloud platform. But I am not able to see any logs in gateways system.

Kindly let me know or help me to fix this issue. This is very urgent

Common Master data and Master data for access control, access analysis in IAG

2024-04-05T22:14:09.627000+02:00

I am implementing IAG for one of my clients. I have most of the configuration but am stuck at maintenance of common master data and master data separately for access analysis, access control and PAM. I am not sure where do I have to maintain that data. Any help will be highly appreciated.

Unable to load metadata of fiori apps in WebIDE.

2024-04-10T06:35:13.212000+02:00

Hello SAP Experts,

I'm unable to load metadata of fiori apps in WebIDE, but when we cross-check this issue in Development, Quality and Production metadata gets load. so facing this issue locally in WebIDE. see the below error which gets display while loading metadata.

error :

javax.net.ssl.SSLHandshakeException: Received fatal alert: certificate_expired

Please look into this issue and provide solution asap.

Thank you in advance.

SAP Cloud connector uninstallation error

2024-04-19T13:08:56.030000+02:00

Can any one help me am unable to uninstall cloud connector

Attaching the screenshot while uninstalling cloud connector as administrator. The process is keep on going

and no progress. If I cancel it cloud connector again coming back t

Thanks

Vykuntarao

Cloud Connector with Error 425

2024-04-23T23:54:43.976000+02:00

Hello Team!

I'm trying to create a new connection settings using cloud connector.

I did logon to access Cloud Connector trought URL as usual
On the left panel, I selected "Cloud to on-premise"

Under Access Control tab, I click in add (+) in order to create a new connection configuration and then I receive the follow error box:

"425 An internal error occurred. See ''Log And Trace Files'' and in particular ljs_trace.log for details"

(See attached file)

Checking log file I did not found nothing regarding this error and even doing a search about this specific error I did not have lucky.

Does any one know something about this error message, any tips?

Thanks in advance.

SAP Datasphere Cloud Connector

Consuming on-Premise Service in CAP Project

2024-04-25T15:34:02.977000+02:00

Hi Team,

I am trying to consume an on-premise service in the CAP project using the destination. My SAP BTP Subaccount is connected to on-premise system via Cloud Connector.

In my existing CAP project, I have added the External Service (on-premise) by following steps as --> Service Center > Select Provider as 'SAP SYSTEM' > Catalog of Services as <my on-premise system> > Selected the service that I want > Selected the Entity that I wanted to add in my existing CAP project. (as shown in below screenshot)

Once service has been added in the CAP project, then automatically one 'external' folder along with one .cds file & one .js file got added in srv folder and in package.json file below changes got added.

( below code is in package.json > cds > requires )

Then I have build & deployed the MTA project. When I run the external service from the deployed applications at space level then I am getting 502 error as 'Error during request to remote service: Failed to load destination.' (as shown in below screenshot)

Note - 1) This destination is used by UI team where it is working fine. 2) We are not able to get the service data even in local testing by cds watch.

Thanks in advance!

Connectivity guaranteed with Cloud Integration version and Cloud Connector version

2024-05-09T02:53:18.355000+02:00

Is there any reference where I can check connectivity guaranteed between BTP Cloud Integration version and Cloud Connector version?

Denying access for user to resource /sap/bc/adt/discovery on system

2024-05-14T08:05:35.802000+02:00

If you encounter a connection error via a cloud connector, one possible reason could be that subpaths have not been granted access permissions. Below is a common error message you might see:

Denying access for user **** to resource /sap/bc/adt/discovery on system ****

To resolve this issue, consider the following steps in your configuration:

Update Your Destination Configuration: Ensure that your destination configuration includes "dev_abap" and "ui5_execute_abap" as values in the WebIDEUsage additional property.
Enable the Necessary Service: Verify that the service /sap/bc/adt/ is enabled in your backend system. This can typically be done via the transaction SICF.
Adjust Access Control Settings: Navigate to the 'Cloud To On-Premise' menu and select the 'Access Control' tab. Here, make sure to grant access to the necessary subpaths. Configure your settings as shown in the screenshot below to ensure the problem is resolved.

By following these steps, you should be able to address most connection issues related to cloud connectors effectively.