Syclo Work Manager 6.1 SSL Configurations

[kulksari]

Hello Experts,

We have an "Communicaiton Error 14" on Device and ATE. I have worked on WM 5.2 and 6.0 and aware of the SSL configurations. I have Generated a Self Signed Certificate and a PFX file using OpenSSL. Now, with SMP 3.0 SP03 we are not able to find how to configure the Agentry.ini and where to copy the .sst file.

Can someone help us understand on how to make this work??? Is there a workaround for HTTP communication without SSL and any document on this which can help.

Is SSL/pfx mandatory to have in 6.1 while testing with ATE?

Regards,

Sarika

[Former Member · Accepted solution]

See: 

[kulksari]

HI

Based on your input we found out what is the issue. Our issue was related to FQDN and certificate error, we got it corrected. Your response was very helpful.

Thank you Stephen and Bill.

Regards,

Sarika

[Former Member]

Hi Sarika,

Can you please let me know how did you resolve the FQDN issue.

I am facing similar issue when using ATE.

Requesting Public Key from Server

Connect to server '192.xxx.x.x', certificate is for 'JILAN.WirelessAP', so it is not valid

Communications error (14)

Connection failed

Ending transmission

I believe JILAN.WirelessAP is the FQDN which SMP is considered.

Can you please let me know if you have resolved similar?

Thanks,

Jilan

[Former Member]

Jilan,

It looks like you entering the IP address into the Server Address name instead of the FQDN.  Can you use the FQDN instead?

Stephen

[Former Member]

Hi Stephen,

Yes, I have to change the FDQN name to IP to work with Management console, only I will get logon screen.  Similarly I have tried to do the same in ATE & WPF client.

in Management Console, while have FDQN in URL,

https://jilan.wirelessap:8083/Admin/

the error is below. But when I change to IP it works.

This page can't be displayed

• Make sure the web address https://jilan.wirelessap:8083 is correct.
• Look for the page with your search engine.
• Refresh the page in a few minutes.
• Make sure TLS and SSL protocols are enabled. Go to Tools > Internet Options > Advanced > Settings > Security

Similarly, in WPF/ATE, if FDQN is in URL, I get the Communication Error(14).

Requesting Public Key from Server

Communications error (14)

Connection failed

Ending transmission

Is any mapping needed in my laptop between FDQN to IP address?

Thanks,

Jilan

[Former Member]

Did you import the smp_crt.cer file into the trusted Root Certificate Store?

Stephen

[Former Member]

Yes I did that Stephen.

While doing, i had to option to choose, current user or local machine, i have installed same .cer file for twice for both options.

Still, i get the Communication error(14).

Will there be any further logs or any other checks?

Please suggest.

Thanks,

Jilan

[nageshcaparthy]

Hi Jilan,

Did you install it on the device also? If you are testing it on the System please check your Certificate deployments in MMC and ensure you delete the old certificate which may create conflict. We had this issue once.

Also please create a new thread.

Regards,

Nagesh

[Former Member]

Thanks Nagesh. Thats a good tip.

For the others, if you refer this thread,

The problem i was facing was , our SAP, SMP was deployed cloud. We were trying to connect from WPF, ATE from local systems, where another version of SMP 3.0 and its respective certificates were installed.

Solution: i have to copy the SMP 3.0 Cloud version Certifiate on the system & install again to work with WPF and ATE.

Many Thanks,

Jilan

[kulksari]

HI

Based on your input we found out what is the issue. Our issue was related to FQDN and certificate error, we got it corrected. Your response was very helpful.

Thank you Stephen and Bill.

Regards,

Sarika

[Former Member]

Sarika,

I am glad to hear that the issue is now resolved.  Can you mark one answer as "Correct Answer" to close the thread so others know what was helpful if they look later?

Stephen

[bill_froelich]

Sarika,

If you are using SMP 3.0 SP03 on the server then you need to be using an Agentry 7.0.3.x client.  You should not be using anything from Agentry 6.1.

With SMP 3.0 we don't use the .pfx anymore and instead use the certificate from the SMP 3.0 server.  Check the link Steve mentioned for more details.

--Bill