Workflow Soluiton

Dear All,

Does anyone know what I can do to get a workflow to be published in HTTPS, aside from saying that the Workflow uses SSL? Do I need to set up certificates, etc for the server and are there any other ancillary tasks?

Kindest regards,

QuietLeni

In order for SSL to work, you MUST have a certificate on the server. No Cert, no SSL. There is a private Key in the certificates that is used to encrypt the data in transport.

In the desginer, I don't think there is much you can do to define HTTPS, that is usually done at the IIS level.

When you are doing the install on the server, check the USE HTTPS box, and make sure your certificate Subject matches the URL you plan to use when you publish your projects.

In INETMGR, right click on the Default Website and edit the bindings. Remove the binding for port 80, and add the binding fot HTTPS/443 with the exiting certificate. This will foce all the published projects to be HTTPS.

You can also set SSL per project, but it is a manual process. You can right click on the project Virtual Folder in IIS and under Bindings, you can bind to the SSL cert. You should also remove the Binding to port 80 to prevent users from connecting to the non SSL port.

Rob

Rob,

Thanks for that. Just one last thing - the Workflow Server and the Notification Server are BOTH on the same box for a sandbox testing environment. In Production, they MUST be separate, yes?

Kindest regards,

QuietLeni

Well, technically no. You can run them both on the same server so long as they each have a seperate Root Website and different ports...

However, Symantec strongly recommends against this. The NS load can increase dramaticaly depending on what is going on and what time it is, and that will negatively impact WF performance. I would also strongly recommend putting WF on a differnt server!

rob