08-22-2016 07:37 AM
Can Act! Connect Link run on a system running Act! Web? Support says no but I don't see why it wouldn't work. Let's say a client has Act! Web and they use it internally. They don't have ports forwarded on their firewall and don't own an SSL cert. Can they install and utilize Act! Connect Link on their server?
09-03-2016 10:27 AM
Even though this is not supported, you can use Act! Connect Link with Act! Web as well. Recommend that the Act! Web API hosted service be turned off. Act! Connect Link by default will access sites on port 80, so it should just work. Just browse to the Act! Connection Link registered URL.
FYI: Act! Connect Link will require external access so its port cannot be blocked by the firewall.
09-06-2016 05:37 AM
Thanks for the reply. Can you check out support case 8010538689 and tell why we had to remove Act! Web and install Act! Premium in order to get Act! Connect Link to work? Also, I'm confused on your comment about port 80. Doesn't Connect Link provide access to the API via SSL (443)?
09-06-2016 07:20 AM - edited 09-06-2016 07:22 AM
Act! Connect Link is a service that provides secured access to a local unsecured service.
If I understood your question correctly, I was assuming you were hosting Act! Premium Web in IIS without a SSL Cert on port 80. Act! Connect Link can route request to any port (configurable), but by default it routes to any local services running on port 80.
I apologize if I misunderstood the question.
09-06-2016 10:58 AM
I'm confused. What you outlined below would require IIS on the host machine (not a requirement for Act! Connect Link). It looks like your describing a hybrid of Act! Connect Link and Act! Web API. My understanding is that Act! Connect Link does not require port forwarding on a network firewall but you may be indicating below that it does.
09-06-2016 11:25 AM
Act! Connect Link does not require port forwarding on a network. Act! Connect Link works by making an outgoing connections to a server, through which traffic can be funneled back into a specified local service. If you have outgoing filtering enabled, you may need to adjust your rules to allow TCP connections for the client to port 22 (ssh port) and 3014 (ACL back channel port).
It was my misunderstanding that we were talking about the API being hosted in IIS. You are right, IIS is not required, it can be hosted in other ways.