Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

SSL problems

Former Member
0 Likes
480

Hi,

I'm fighting with sapcryptolib. Installation is ok, in ICM trace I've got message that sapcryptolib is ready, so I think the problem is somewhere in certificates. My settings here:

[ICM trace|http://img688.imageshack.us/img688/4237/tracevn.jpg]

[strust|http://img442.imageshack.us/img442/3503/trust.jpg]

[rz10|http://img188.imageshack.us/img188/295/rz10.jpg]

I started https on port 8102 and on windows command 'netstat -a' shows:

TCP 0.0.0.0:8102 0.0.0.0:0 LISTENING

TCP 0.0.0.0:8102 0.0.0.0:0 LISTENING

double. With other ports it's single.

I can't display any page by https. http works normally. I used burp proxy to check what's happening and it threw:

'Remote host closed connection during handshake'.

This is a test-server so it is not in a domain. I use it only by IP, so what should I write in CN = ?

I went through notes 510007, 662340 and /people/gregor.wolf3/blog/2005/10/11/setup-https-ssl-for-the-sneak-preview-sap-netweaver-04-abap-edition-on-windows

every time it is the same problem.... Is there any logs where I can find what happens when I try to open page by https? I have no ideas what to look for. Regarding to notes it just should work..

1 ACCEPTED SOLUTION
Read only

Former Member
0 Likes
425

Hi,

From your screen shots, your configuration seems OK to me.

Increase the trace level from transaction SMICM and look into it after a test.

Check also if another software is not already using the same TCP/8102 port.

Regards,

Olivier

2 REPLIES 2
Read only

Former Member
0 Likes
426

Hi,

From your screen shots, your configuration seems OK to me.

Increase the trace level from transaction SMICM and look into it after a test.

Check also if another software is not already using the same TCP/8102 port.

Regards,

Olivier

Read only

0 Likes
425

I set port to 11111 and it started working... Thank you for the clue.