Connections
A connector configured against a real system — over HTTPS, or directly over the network (a VPN or interconnect) to a database, directory or service port. Every handshake is TLS 1.2 or higher and the server is verified, against a trusted root or a CA you upload under Certificates. Credentials are encrypted on the way in and never come back out — only the last four characters are ever shown. A connection here carries data; it does not place Microsoft Teams calls or create meetings — those run through CRM › Interaction Centre › Connected Channels, and testing a Teams connection here says what that still lacks.
Where to find it
- Module: Platform
- Group: Connectivity
- Section: Integration
- Screen: Connections
Address in the console: /platform/connections
List · 17 columns · 18 fields on its form · 3 of them required · 3 actions
What the list shows
These are the columns of the list, in the order they are drawn. Any of them can be sorted on, filtered on, hidden, or exported.
| Column | Kind | Field name |
|---|---|---|
| Connection | Code | code |
| Name | Text | name |
| Connector | Text | connector_name |
| Category | Status | category |
| Environment | Status | environment |
| Transport | Status | transport |
| Endpoint | Text | endpoint |
| TLS | Code | tls_protocol |
| Direct connect | Status | direct_connect |
| Auth | Status | auth_type |
| Credential | Status | credential_kind |
| Secret | Code | secret_last4 |
| Status | Status | status |
| Endpoint warning | Text | host_warning |
| Tested | Date and time | last_tested_at |
| Health | Status | health |
| Last test result | Text | last_test_message |
The form
What is asked for when a record is created here. Required fields are marked; a choice drawn from a configuration list is one an administrator can extend without a release.
| Field | Type | Choices | Notes |
|---|---|---|---|
| Connection code required | Text | ||
| Name required | Text | ||
| Connector required | Choice | Looked up from existing records | |
| Environment | Choice | Configuration list | |
| Transport | Choice | https, direct | https = an endpoint URL. direct = straight to a host and port over the network (VPN, interconnect, peering) — a database, a directory, a service port. |
| Endpoint URL | Text | HTTPS only (TLS 1.2 or higher), in every environment. For a https connection. | |
| Host | Text | For a direct connection: the name or address only, e.g. hana.corp.local or 10.20.0.15. | |
| Port | Number | For a direct connection, e.g. 5432 PostgreSQL, 1433 SQL Server, 30015 HANA, 636 LDAPS. | |
| Protocol | Choice | tls, postgres | tls = TLS from the first byte (LDAPS, HANA, SQL Server with strict encryption, SMTPS, AMQPS, Kafka). postgres = PostgreSQL, which negotiates TLS on connect. |
| Lowest TLS version | Choice | TLSv1.2, TLSv1.3 | TLS 1.2 is the floor; nothing older can be chosen. |
| Server name | Text | Only when the certificate names a different host from the one connected to (SNI and verification). | |
| Trusted CA | Choice | Looked up from existing records | For a server whose certificate is issued by your own CA. Empty = the public roots. |
| Client certificate | Choice | Looked up from existing records | Presented to the server (mutual TLS). Needs its private key stored. |
| Pinned fingerprint | Text | Optional. The server certificate’s SHA-256 fingerprint; any other certificate is refused. | |
| Username | Text | Basic authentication only. | |
| Configuration | Text | ||
| Owner | Choice | Looked up from existing records | |
| Exception reason | Long text | Administrators only, and only when this connection must point at a public request bin or tunnel (webhook.site, ngrok and the like): say why. It is kept with the connection and in the audit trail. |
What you can do here
Test primary
Test this connection
Check direct connect
Can this system be reached directly?
Asks for: Also try port
Set credential
Store the credential
Asks for: Client id* Client secret* Token URL* Scopes Audience Signing secret* Header name Client certificate (PEM)* Private key (PEM)* CA certificate (PEM) API key* Username* Password* Token* Credential*
* required
The rules that apply here
Everything on this screen obeys the platform rules rather than rules of its own. The ones worth knowing before you use it:
- Narrowing a list — search, conditions, sort, totals, export and saved views.
- What may be changed — the five grounds a record may not be edited on.
- Companies and business units — what the switcher above this list is doing to it.
- Creating a record — required fields, where choices come from, and how the number is allocated.
- Importing a spreadsheet — this screen accepts one, and it runs through the same rules as typing.