WebConfig - Add or Edit a Port

Server Port

Defines the Port number that the Pro Cloud Server will listen on for HTTP/HTTPS connections.

Each defined Port must be unique and not used by any other service or application on the current machine. The standard HTTP Port (80) and HTTPS Port (443) are no different; if they are available, the Pro Cloud Server can be configured to use them. You can use the Windows Resource Monitor (which is accessibly via an icon on the Configuration Client 'Ports' tab) to check which Ports are already in use.

Firewall Note: When changing or adding a new Port, check that incoming requests are allowed by the firewall settings at both the local machine and network levels.

Wine Note: When the service is running on Wine you should not use privileged Ports - those below 1024; under Wine, most applications are only able to listen on ports above 1024.

Protocol

Select the transfer protocol that the Port communicates on.

When selecting HTTPS you can also specify which versions of SSL/TLS are allowed, by selecting the relevant checkboxes.

Important: For HTTPS to be configured correctly, a file named server.pem must also exist in the same directory as the configuration file, and it must contain a valid private key/certificate. See the Using HTTPS (SSL) Help topic for details.

WebEA / OSLC Supported

If checked, this flag enables OSLC requests on the current Port.  Note: this option must be selected for WebEA access.

Authentication

Select the type of authentication that will be required for this Port:

Model - All model connections that use the current Port will be forced to request HTTP authorization using the user security defined in the Enterprise Architect model being connected to. Passwords must be explicitly and individually assigned in that model using the Maintain Users procedure; the default administrator password and any passwords imported from Windows Active Directory do not work.

Note: If you are not using HTTPS/SSL to connect, the usernames and passwords will be sent in plain text.

If the model does not have security enabled, the Cloud user is not prompted for a password.

Global - Selecting this option enables the 'Global Authentication Model' field. In this field enter the DB Alias of Data Manager that will be used to provide the security profile to all connections opened with the current Port.  This is helpful if you want to provide multiple repositories but only manage one list of users. Passwords must be explicitly and individually assigned in the Global model using the Maintain Users procedure; the default administrator password and any passwords imported from Windows Active Directory will not work.

Note: If you are not using HTTPS/SSL to connect, the usernames and passwords will be sent in plain text. Sparx Systems recommends that Global authentication should only be used with the HTTPS protocol.

Global Authentication Model

Required when the 'Authentication' option is set to 'Global'.