HTTPS configuration with Product Point M030

[Marc-AntoineLem]

Hi all,

Anyone configured the HTTPS for Product point ? I read the doc and seems that we need to have a special ISA server or something (Another item that the sales guy doesn't tell you).

Thanks

Marc

[LarsBjors]

Hi

I am working on an installation now (actually have worked since may 2010) and come as far as having a https site running on the server. I am able to see it using a web browser on the server, but its not available in the client browser. This is a IT problem so I presume that it will be fixed soon.

I have had a discussion with PTC support about using HTTPS and according to the document you refer to (Configuring an Extranet Server for External Collaboration) its only possible to use HTTP to connect ProE:

Windchill ProductPoint currently only supports HTTP Integrated authentication when using Pro/ENGINEER through the ISA server

Note

: Currently, Windchill ProductPoint with Pro/ENGINEER only supports HTTP Integrated authentication.

But there is also a TAN 150403 stating that its possible to open parts from a HTTPS in ProE:

Description

Open in Pro/ENGINEER action is unable to open a part from a secure (HTTPS) Windchill ProductPoint server.

Resolution

See Alternate Technique.

Alternate Technique

Use the following procedure when opening a Pro/ENGINEER part that is on a secure Windchill ProductPoint HTTPS server:
1. Open Pro/ENGINEER.
2. In the Server Manager (Tools > Server Manager), register the secure Windchill ProductPoint server. The registration is interrupted by a pop-up Security Alert window.
3. In the Security Alert window, click Yes (to proceed).
4. From the server Downloads page, download and install the Windchill Product Point Client Manager.
5. After installation has completed, close the Windchill ProductPoint Client Manager window.
6. From Windows, start the Client Manager (Start > All Programs > Startup > Windchill ProductPoint Client Manager). After this initial, manual startup, the Client Manager is automatically started with Windows at future startups.
7. With the Client Manager running, retry the registration of the server. This time registration completes.
8. Navigate to the part that you want to open.
9. From the Actions menu for the part, select Open in Pro/ENGINEER.
10. In the Security Warning window that opens, select ‘No’ so that you view both HTTPS and non- HTTPS content. (Note: Requests made to the Client Manager are properly under HTTP.)The part successfully opens in Pro/ENGINEER.

So I will keep on working with this and let you all know.

/Lars Björs

[LarsBjors]

Hi

To make this seem like a discussion I will reply on my own entry.

Yes we were finally able to make it work. The main obstacle was to make ProE register the https server. What finally made it possible was:

1: Register the https port = 443 in the IIS and bind the certificate to that port

2: Remove the port 80 entry in the IIS.

3: Have a certificate with the right server name.

4. Edit the DNS so it point to the right site.

5: Make sure that all users are working.

So to use it internally with https there is no need for an ISA server

So next question is how to make Sharepoint index 443 instead of 1975. Anybody who knows this?

/Lars Björs

[Marc-AntoineLem]

We finally decided to install a VPN over the entire network.

It work just fine

MA

[LarsBjors]

So

The final answer was Alternate Access Mapping.

I changed the default entry to the https:// name and the :1975 to Intranet.

When I restarted the server I noticed that the https: adress was used for search. Look in the registry for adresses that are crawled. My humble conclusion is that only the default entrys are crawled.

Note that this is was about using Https inside the company (acctually in this case, inside the university)

/Lars Björs

Econocap