Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

CONNECT flows

Local endpoints

  • Last UpdatedNov 02, 2026
  • 3 minute read

A flow runtime uses three local endpoints:

  • Port 8883: The internal MQTT Broker (MQTTS) configured in mqttconfiguration.json.

  • Port 9090: Used to exchange data with flows, through the HTTP Listener/Response modules (HTTPS), and configured in httpconfiguration.json.

  • Port 9191: Admin API (HTTPS) configured in endpoints.json

Default authentication for flow runtimes

The default configuration sets up basic authentication (username/password) for all endpoints. A default admin user is created for the admin API. Before accessing the API, you must set the password through the "EDGENODE_API_DEFAULT_ADMIN_PASSWORD" environment variable.

To use the flows endpoint (port 9090) or MQTT (port 8883), additional users must be added through the API. For development and testing, disable authentication by setting "AuthenticationType" to "None" in the corresponding configuration files or through environment variables. Remember to enable authentication after testing is done.

A self-signed Secure Sockets Layer (SSL) certificate auto-creates when the runtime starts. You can reference custom certificates from the configuration files for the corresponding endpoints.

To communicate with a flow using HTTP on port 9090, at least one user must be added using basic authentication. This is done through the admin API.

The following code example shows how to create a user using Client URL (cURL) in Windows PowerShell.

# Host API administration on port 9191
$apiBaseUrl = 'https://127.0.0.1:9191'
$apiCredential = 'admin:api-admin-password'

# New HTTP listener user — use a strong real password
$httpUsername = 'flow-http-client'
$httpPassword = 'replace-with-a-strong-password'

# Get a CSRF cookie and request token for the API-admin user.
$cookieFile = Join-Path $env:TEMP 'flow-host-api-cookies.txt'

$tokenResponse = curl.exe -k -sS -u $apiCredential `
   -c $cookieFile `
   "$apiBaseUrl/api/antiforgery/token" |
   ConvertFrom-Json

$csrfToken = $tokenResponse.token

# Create the HTTP-category user.
curl.exe -k -i -u $apiCredential `
   -b $cookieFile `
   -H "X-CSRF-Token: $csrfToken" `
   -H 'Content-Type: application/json' `
   -X POST "$apiBaseUrl/api/users" `
   -d "{`"username`":`"$httpUsername`",`"password`":`"$httpPassword`",`"category`":`"HTTP`"}"

Remove-Item $cookieFile -ErrorAction SilentlyContinue

Cross-Origin Resource Sharing (CORS) configuration

With the default configuration, CORS is turned off on the HTTP endpoint (9090). To enable CORS, the following settings are available in the httpconfiguration.json file.

Parameter

Description

Default

EnableCors

Turn on/off CORS

false

CorsOrigins

Specifies the origins permitted to access the endpoint. An origin consists of a scheme, hostname, and port, such as https://app.example.com.

[ ]

CorsAllowCredentials

Determines whether cross-origin requests can include credentials, such as cookies, HTTP authentication or client-side TLS certificates.

false

CorsAllowedMethods

Specifies which HTTP methods are allowed for cross-origin requests, such as GET, POST, PUT, PATCH, and DELETE.

[ ]

CorsAllowedHeaders

Specifies which HTTP request headers the browser is allowed to send in cross-origin requests, such as Authorization, Content-Type, and X-Custom-Header.

[ ]

CorsMaxAge

Specifies how long, in seconds, the browser may cache the result of a CORS preflight request, reducing the need to send repeated preflight requests.

3600

Custom certificates

With the default configuration, the flow runtime creates a self-signed Transport Layer Security (TLS) certificate. Custom certificates can be used, either from a local certificate store or a file. The following settings are available in the httpconfiguration.json and mqttconfiguration.json files, for the respective protocols.

Parameter

Description

Default

CertificateType

Selects the endpoint certificate mode: None (no TLS certificate), AutoCreated (self-signed localhost certificate), FileCertificate (load from a file), or StoreCertificate (find in a certificate store).

"AutoCreated"

ClientCertificateRequired

Requires connecting clients to present a certificate during the TLS handshake (mutual TLS).

false

StoreCertificate:

Subject

Subject name used to find a certificate in the selected store.

""

StoreName

Certificate store to search, such as My (Personal).

"My"

StoreLocation

Store location to search: LocalMachine or CurrentUser.

"LocalMachine"

AllowValidOnly

If true, only certificates considered valid by the platform’s certificate search are returned.

true

SslProtocols

TLS protocol selection for the store certificate. None means the operating system chooses the enabled protocols.

"None"

FileCertificate:

CertificatePath

Path relative to data/certificates under the flow runtime’s current working directory. The file must be PKCS#12 format, typically .pfx or .p12.

""

CertificatePassword

Password for the PKCS#12 certificate file, if required.

""

SslProtocols

TLS protocol selection for the file certificate. None means the operating system chooses the enabled protocols.

"None"

CertificateExpirationDate

Read-only value populated from the loaded certificate’s expiration date, in UTC. It is null when no certificate is loaded; it is not a configuration setting. It may support status/reporting, though I found no consumer in the current source.

null until a certificate is loaded

In This Topic
Related Links