SEAL & PCT2

[Adam_Tri-M]

Anyone know how I can get SEAL to connect to a PCT2 server?

Seems to need a certificate, which I don't think we can generate on PCT2.

And won't allow non-secure connections from what I can tell.

Ideas?

[StefanLundin]

Hi,

PCT2 and SEAL should work just fine. And yes, you should use non-secure communication—I have that setup on my machine.

There were some EBO/PCT2 combinations (prior to EBO 6.0) that required a workstation hotfix, according to the PCT2 release notes. If that wasn't fulfilled Seal could not setup a communication.

Please check this link if that applies to your case:

https://community.se.com/t5/EcoStruxure-SEAL-Forum/Connecting-to-PCT-server-issue/m-p/507217#M262

[Benji]

@Adam_Tri-M thanks for playing with SEAL 🙂 As @StefanLundin notes, it most definitely works with PCT. In the thread @StefanLundin is linking to, I've shared a document created by the GEC team: https://community.se.com/t5/EcoStruxure-SEAL-Forum/Connecting-to-PCT-server-issue/m-p/507235/highlig...

Please feel free to share anything you work with or come across

[Adam_Tri-M]

I didn't think to remove the full https:\\ - i was changing it to just http:\\ in the address field. 

But my other issue was that our PCT2 server has a DNS name we normally use to connect to. 

However, my guess is the SEAL (and AET) cannot resolve that name.

Once I used the actual IP Address, I was able to connect.

Thanks all!

And again - this tool looks awesome. Creating a new script to do some auto binding as we speak!

[Benji]

Nice!!!

[APA]

Secure connection works with PCT2, you need to have the certificate installed to PCT2. After that the secure connection works, and you don't have to generate certificates in EBO Servers.

I have FQDN certificate installed on PCT2 and pct2.local points to 192.168.10.2 on my hosts file.

[Adam_Tri-M]

If memory serves, I tried to do that, but my IT department didn't want to go thru the hassle of getting a 256 certificate - the normal ones are 512. Again - if I remember correctly.