Server and Firewall Configuration

This topic describes what server and firewall settings allow users to connect to the K2API.

Connection Port

The connection port you use depends on how your firewall is set up. If the firewall uses the standard HTTPS port of 443, you can ignore this setting.

Firewall Setup

These are the recommended values and assume ports in IIS have not been changed from the installer defaults. In all cases, the firewall needs to match requests in the format "[scheme]://[domainname]/K2API/*", "[scheme]://[domainname]/Identity/sts/Forms/*" and "[scheme]://[domainname]/Runtime/*" where [scheme] is HTTP or HTTPS and [domainname] is the public DNS name.

The above request URIs need to be added to accommodate the SmartForms authentication runtime for Security Token Service (STS) login, using forms authentication, this in turn will use the SmartForms runtime cookie.

K2 recommends that you configure SSL in IIS before installing so that the installer can use those SSL bindings for the K2 site, including the K2API. For a general guide to firewall ports and K2, see the article K2 and Firewalls (KB001318).

External Access

A DNS record in a public name server with an A (or AAAA) record that points to your IP address. It is assumed that your IP address is static (dynamic DNS could be used but is not recommended). If your IP address is not static, K2 recommends you purchase a static IP from your ISP who may also be able to provide you with DNS services.

You can position the K2Api behind a load balancer if required.