"gatewaySetting" is serialized incorrectly inside "connectionParameterSets"

[afreeman-sherwin]

Severity

P2 - High (Major functionality broken)

Describe the Bug with repro steps

Expected Behavior

When a selected parameter set contains gatewaySetting, LogicAppsUX should serialize it using the gateway-compatible connectionParameters shape, or the gateway connection API should accept the connectionParametersSet representation.

Actual Behavior

A custom connector using connectionParameterSets cannot create an on-premises gateway connection because the selected gateway parameters are serialized as connectionParametersSet values.

Reproduction

Define a parameter set containing authType and gatewaySetting:

{
  "name": "gateway-noauth",
  "uiDefinition": {
    "displayName": "Gateway",
    "description": "Connect through the on-premises gateway."
  },
  "parameters": {
    "authType": {
      "type": "string",
      "uiDefinition": {
        "displayName": "Authentication Type",
        "description": "No authentication",
        "constraints": {
          "required": "true",
          "allowedValues": [
            {
              "text": "No authentication",
              "value": "anonymous"
            }
          ]
        }
      }
    },
    "gateway": {
      "type": "gatewaySetting",
      "gatewaySettings": {
        "dataSourceType": "CustomConnector",
        "connectionDetails": []
      },
      "uiDefinition": {
        "displayName": "Gateway",
        "description": "Select a gateway.",
        "constraints": {
          "required": "true",
          "capability": ["gateway"]
        }
      }
    }
  }
}

Actual Payload

LogicAppsUX submits:

{
  "properties": {
    "connectionParametersSet": {
      "name": "gateway-noauth",
      "values": {
        "authType": {
          "value": "anonymous"
        },
        "gateway": {
          "value": {
            "id": "/providers/Microsoft.PowerApps/gatewayClusters/<gateway-id>"
          }
        }
      }
    }
  }
}

The request fails with:

The 'authType' connection parameter is null or invalid for the on-premise connection request.

Working Payload

The Power Platform custom connector wizard creates successful gateway connections using:

{
  "properties": {
    "connectionParameters": {
      "authType": "anonymous",
      "gateway": {
        "id": "/providers/Microsoft.PowerApps/gatewayClusters/<gateway-id>"
      }
    }
  }
}

Relevant Code

libs/designer-v2/src/lib/ui/panel/connectionsPanel/createConnection/createConnectionInternal.tsx

The current parameter-set serializer wraps every parameter in a value object:

values: Object.fromEntries(
  Object.keys(filteredParameterValues).map((key) => [
    key,
    { value: filteredParameterValues[key] },
  ])
)

This serialization is incompatible with the gateway connection API's expected flat connectionParameters contract.

What type of Logic App Is this happening in?

Standard (Portal)

Are you experiencing a regression?

No response

Which operating system are you using?

Windows

Did you refer to the TSG before filing this issue? https://aka.ms/lauxtsg

Yes

Workflow JSON

Screenshots or Videos

No response

Environment

• Microsoft Power Automate
• Custom connector deployed with paconn
• Microsoft on-premises data gateway, standard mode

Additional context

No response

[github-actions]

AI Triage Analysis

Component: Connections (createConnection panel) | Priority: P2 → priority:high | SKU: Standard (Portal)

Relevant Code

• libs/designer/src/lib/ui/panel/connectionsPanel/createConnection/createConnectionInternal.tsx:L364-L379 — getConnectionParameterSetValues wraps all parameter values in { value: ... }, including gatewaySetting types
• libs/designer-v2/src/lib/ui/panel/connectionsPanel/createConnection/createConnectionInternal.tsx:L372 — Same function exists in v2; same issue
• libs/logic-apps-shared/src/utils/src/lib/models/connector.ts:L20 — gatewaySetting is a recognized ConnectionParameterTypes value
• libs/designer/src/lib/core/actions/bjsworkflow/connections.ts:L791 — gatewaySetting is listed in SupportedConfigConnectionParameterTypes, indicating it should use flat connectionParameters serialization

Probable Root Cause

Code search confirms the issue. getConnectionParameterSetValues (in both designer and designer-v2) unconditionally wraps every parameter value in { value: ... } and packages everything under connectionParametersSet. However, when a connectionParameterSet entry contains a gatewaySetting-typed parameter, the gateway API expects the flat connectionParameters payload shape (the same shape used when no parameter set is selected). The fix likely requires detecting whether any parameter in the selected set has type gatewaySetting and, when true, falling back to (or merging into) the flat connectionParameters key instead of connectionParametersSet.

Suggested Investigation

1. In getConnectionParameterSetValues, check if any key in filteredParameterValues corresponds to a gatewaySetting parameter type. If so, return undefined for connectionParametersSet and populate connectionParameters with the flat values instead (matching the working Power Platform payload).
2. Verify how the caller in createConnectionInternal.tsx constructs ConnectionCreationInfo — the connectionParameters field already exists and would receive the flat values; it may just need the guard condition added.
3. Confirm fix applies to both libs/designer and libs/designer-v2 (the function is duplicated).

---

Automated analysis by issue triage agent. May contain inaccuracies — verify before acting.
Calibration: reviewed 10 past triages, 0 corrections found (no prior feedback comments detected).

Generated by Issue Triage Agent for Azure Logic Apps UX for #9559 · sonnet46 43.2 AIC · ⌖ 7.09 AIC · ⊞ 11.1K · ◷

[rllyy97]

Thanks for the detailed repro and payload comparison. I independently traced the request path and reproduced both wire shapes locally without Azure credentials or customer data.

What is confirmed

• When a connectionParameterSet is selected, both designer generations build connectionParametersSet, and the shared API Hub client intentionally sends it as properties.parameterValueSet with { value } wrappers.
• When no set is selected, the same client already sends the flat properties.parameterValues shape.
• A credential-free Playwright service-boundary repro captured both exact PUT bodies: the issue fixture produced parameterValueSet and omitted parameterValues; the flat fixture produced parameterValues and omitted parameterValueSet.
• Existing public SQL Server, SAP ERP, and SAP OData definitions contain gatewaySetting inside parameter sets and depend on gatewaySettings.credentialType plus parameterValueSet to select the gateway authentication branch. Flattening every gateway-bearing set would regress those supported connectors.
• The official paconn schema and the certified Connect Bridge custom connector instead use flat connectionParameters for authType + gatewaySetting.

The provided fixture combines these two contracts: authType + gatewaySetting are inside a named parameter set, but the gateway metadata has no credentialType. That explains why the current API Hub request follows the set contract while the gateway service cannot resolve the expected auth type. It does not yet establish that LogicAppsUX should flatten the set: the working Power Platform example may use a different connector definition and/or a different resource-provider endpoint.

Why I am not applying the automated triage suggestion

A blanket fallback based only on the presence of gatewaySetting would also flatten known-working SQL/SAP parameter sets, discard their selected set name, and risk breaking Standard local and Consumption authentication handling. There is not currently a safe, authoritative discriminator in the LogicAppsUX model.

Information needed for a safe fix

Could you provide the following sanitized details?

1. The complete deployed connector properties block, including both top-level connectionParameters and the full connectionParameterSets entry.
2. The exact failing request URL/resource provider and API version.
3. Confirmation that the flat working payload succeeded against the same registered connector ID/version and the exact URL/resource provider used for that request.
4. If available, gateway/API Hub Product Group guidance on whether a dataSourceType: "CustomConnector" parameter set must declare gatewaySettings.credentialType (for this case, likely Anonymous) or whether clients are expected to flatten it.

Two connector-side shapes are already known to work: use flat connectionParameters for authType + gatewaySetting (the supported paconn/certified-custom-connector pattern), or define a true parameter set whose gateway metadata supplies the credential type. With the details above, we can determine whether a narrow LogicAppsUX compatibility rule is required and add positive plus SQL/SAP regression coverage without risking existing gateway connectors.