Currently I'm testing the SAP Netweaver GateWay Adapter of version 6.3. It contains a lot more capabilities to interact with SAP.
When connecting to the development environment of SAP, I have to use client-id 1000. Apparently only 3 characters of my client-id are interpreted by the MobileFirst server.
E.g.
1// connecting to sap with client-id 1000 - returns with the following response:
"set-cookie": "sap-usercontext=sap-client=100; path=/",
2// connecting to sap with client-id 2912 - returns with the following response:
"set-cookie": "sap-usercontext=sap-client=291; path=/"
Anyone facing the same problem?
Br.
Wim
From the development team:
We are not aware of any three character limit in the code, however
passing the client ID won't work regardless as it is not being sent to
the server at all due to a defect.
You should open a PMR in order to receive the fix for APAR PI31148.
There is no workaround.
Related
I have been using SSL to connect a SIMCOM SIM800 GSM Module to a Microsoft Azure function endpoint. This has been working for months and has now stopped working and reports a 606 error code which indicates an "SSL alert message with a level of fatal result and the immediate termination of the connection" according to SIM800 Series_SSL_Application Note_V1.02
I tried HTTPS connections to various other sites using the SIM800 e.g. google and httpbin and got mixed results: I could connect to some e.g. google but not others e.g. httpbin. See here for a similar result.
Does anyone know if sites have recently changed SSL cipher or protocol requirements? The SIM800 module (only) supports SSL2.0, SSL3.0 and TLS1.0.
I'm using a SIM808 (V2 / R14.18) to make some GET requests to HTTPS endpoints such a https://www.google.com and a personal Azure website.
I get successful answers from google but from Azure, even if change the "Minimum TLS version" I'm always having a 606 answer.
So, I'm not sure if my SIM808 does really support TLS1.0. Maybe your SIM800 does (documentation is quite confusing).
I kept getting a 606 error while trying to 'GET' my AWS API and I could not figure this out. Reconfigured the custom domain mapping to use TLS1.0 instead of TLS1.2 and communication is now flowing through.
We have an application running on windows 2012 R2 OS with 4.6 framework and database as SQL server 2012. Due to security concerns we were asked to enable TLS1.2 protocol for the calls made between application server to database server and vice versa. I have followed below URL and we have all patches installed.
https://support.microsoft.com/en-us/help/3135244/tls-1-2-support-for-microsoft-sql-server.
Our front end application doesnt directly call the database instead we have WCF service in between front end application (asp.net) and SQL server. I read in an article we can achieve this without making changes to the code and change the providername ="SQLNCI11". When i change the provider name like below i am getting error. saying that "Unable to find the requested .Net Framework Data Provider"
Data Source=servername;Initial Catalog=DBname;uid=XXX;pwd=XXXX;Connect Timeout=200;MultipleActiveResultSets=True;Current Language=us_english; providername="SQLNCI11"
I have verified machine.config and i dont find DBproviderfactory for SQL native client.Am i missing anything here?
As an alternative, Without changing provider name in connection string i have added Encrypt=true;TrustServerCertificate=true in connection string
Data Source=servername;Initial Catalog=DBname;uid=XXX;pwd=XXXX;Connect Timeout=200;MultipleActiveResultSets=True;Current Language=us_english; Encrypt=true;TrustServerCertificate=true providername="System.Data.SqlClient"
After making above changes in connection string database call was success and when i see Ethernet communication using wireshark tool, database to WCF service communication is made with TDS protocol and TLS is involved according to wireshark tool. If i remove "Encrypt=true;TrustServerCertificate=true" from connection string then i dont see "TLS Exchange" message.
What steps should I need to take to ensure the application use TLS 1.2 protocol to communicate with the database? and also please suggest how to prove this communication.
One year later, I wanted to assess the same thing - knowing exactly what TLS version is in use for my MS SQL traffic.
Actually TLS is encapsulated in TDS when it comes to MS SQL traffic.
You can see TDS header (starting by 0x12 - higlighted in yellow in the picture).
After this header begins the TLS packets and you can check version by looking at 2nd and 3rd TLS packets.
In my example, 0x03 0x03 stands for TLS 1.2 (3rd version of TLS protocol)
I am implementing a minimal SUPL 2.0 client. I have added SUPL ASN1 specification and LPP ASN1 specification with my application and compiled it. I am trying to implement a SET initiated Immediate services scenario.
I have filled all the fields to SUPL START message with LPP protocol information and LTE cell id (location id) information. I am sending this message to supl.google.com, but I am not able to receive any response from the google supl server.
Does google supl server support LPP?
I have tried with supl.nokia.com also. Similarly I am not getting any response with nokia supl server also.
The same application code is working fine for RRLP protocol.
Please let me know if anybody has come across the similar issue or have some information regarding LPP protocol usage with google SUPL 2.0 server.
Yes, supl.google.com supports SUPL 2.0 and LPP. What port number are you using for the SUPL connection? I think 7275 is encrypted, 7276 is not. You could implement OpenSSL or other encryption, but I would just use 7276.
Are you setting the LPP capability bit? Are you sure you got all your asn.1 packing and aligning done correctly? RRLP working is a good indicator that you know what you are doing, but I think the usual case for no response is a badly formed message.
I'm trying to find a way to monitor the actual XML being generated and received with some Webservices I am painfully trying to implement on Domino 8.5.3
SoapLog, as mentioned by Julian Robichaux does not seem to work anymore.
The particular case I have here is that I am accessing, server to server (because it's an HTTPS Call), an external Webservice with a Java Web Service Consumer.
Any suggestions?
If you turn on encryption in SAP between the client and the server using the Secure Network Connection, then is there a load placed on the server to do all the encryption work? How big a load? Is it equivalent to the difference between HTTP and HTTPS on a web server?
Please clarify what you want to do.
Do you just want to create secure RFC connections from the SAP GUI to the SAP system? Which 3rd party security product will you be using (e.g. Kerberos).
Will you be using Single Sign On? i.e. via an AD server. If so, where will the secure connection be - full end to end?
With encryption, the main load is during the initial handshaking between the client and the server. During this process, keys are calculated and exchanged.
See the SNC User's Guide for information.
I have not seen any references to the load on the system. I did ask SAP OSS years ago but did not get a satisfactory reply.
You cannot compare the load of SNC (using DIAG) to HTTPS because the protocols are very different - DIAG is a lot leaner.
I have investigated the use of F5 servers. They can be used for software and hardware accelleration of HTTPS, but not for the DIAG protocol.