Lifetime ports

  
What ports are needed for lifetime to work between 2 servers
Hello Derek,

To understand a bit more how LifeTime works, and what are the requirements, you can check the following document:
www.outsystems.com/goto/lifetime-installation-and-configuration-technical-note

Kind Regards
Ivo Gonçalves
Hey Derek.

LifeTime calls some WebServices in ServiceCenter, so, you need to have the 80 port open, unless you have a different port in use.
Hi,

Lifetime will first try to use the https port (443) to extablish a secure channel.
If that is not available (or invalid for ex: bad certificate), then it will try over the http port (80).

Looks like something that should be added to the technote.

Regards,
João Rosado
:)

Thanks João. Seem so, yes... I looked for "port" in the PDF and got no hit on my search...
I'm trying to register an enviroment to Lifetime and im getting the following error.
----------------------------------------------------------
Could not establish a secure network connection between outsystems.server.com and LifeTime (lifetime.server.com).
Sensitive data is sent between these environments. To secure that data, both LifeTime and outsystems.server.com must be configured to use SSL/TLS.
-------------------------------------------------------------

Is it possible to force lifetime to use port 80 instead of 443 ?

Solution
Hi capsuline,

It isn't an error, it's a warning. 
As Rosado said above, Lifetime will first try to use the https port (443) to extablish a secure channel.
If that is not available (or invalid for ex: bad certificate), then it will try over the http port (80).

That warning message is there just to let you know that if you proceed you will not use secure connections when sending data between the LifeTime server and the environment.

If you're Ok about that you can proceed with the registration process, which means that communications between LifeTime and environment will use the http port.
Solution
@Miguel Rebelo Thanks for reply. 

I can not go further as its saying

outsystems.server.com couldn't connect back to the LifeTime environment.

I have open all the ports as stated in the documentation.
Or is it not a port related issue?

Regards



I found the problem. 
IIS was not properly configured.
Its working now. Thanks Miguel Rebelo
Great @capsuline! :)

Don't hesitate to ask if you have any further questions.
Just for future reference, can you say what you've changed for LifeTime to start working?
It's possible that other people have the same configurations you had, and will strugle with the same problem.

Thanks!
capsuline,
What did you do?
capsuline wrote:
I found the problem. 
IIS was not properly configured.
Its working now. Thanks Miguel Rebelo
 
 What did you do?

Hi, I am running into the same problem. Could you please share or refer to a page with the solution?

Hello Jan,


As it was referred, LifeTime uses HTTP (80) or HTTPS(443) to communicate with the environment's ServiceCenter. It will try to connect to HTTPS (443) first, and then fallback to HTTP (80).

What is not referred is that the environment's Service Center needs to be able to connect back to LifeTime using the same protocols (port 80 or port 443).

It's also possible to force the registration to use SSL, which will establish a HTTPS (port 443) connection only, not falling back to HTTP (80).

So you need to guarantee that the LifeTime environment reaches the environment/server you're registering, but also the inverse path (the server reaches the LifeTime).

If you're using HTTPS (port 443), make sure you have valid and trusted SSL certificates in the IIS of both the LifeTime environment and the environment/server you're registering.

If you're not using HTTPS, it will fallback to HTTP (port 80).

To validate the connections, you can access the LifeTime server, and open a web browser and access Service Center of the environment being registered. And then access the environment's server and open a web browser and access the LifeTime.

Hope this information is helpful.

Cheers


Hi Jan,

In my case i had to install a SSL Certificate and bind port 433 to it.
I could not continue without.
attached IIS Manager Site Binding screenshot.

Hope it helps.