Incorrect `type` Value Generated in `connectionparameters.json` for Custom Connector

[cfernandes-muhimbi]

Summary

When creating a Custom Connector inside a Power Automate Dataverse Solution using a Swagger 2.0 definition that includes multiple authentication types (OAuth2 + API Key), the exported solution contains an incorrect property name in the generated connectionparameters.json file.

The generated file uses:

"type": "oAuthSetting"

However, the correct value should be:

"type": "oauthSetting"

Due to this typo, publishing the connector in Microsoft Partner Center fails with the following error message:

“Looks like this is not an OAuth connector. Kindly uncheck the box to proceed further.”

---

Steps to Reproduce

1. Create a new Dataverse Solution.

2. Create a Custom Connector in DataVerse.

3. Inside the Custom Connector:

   • Open the Swagger Editor.

   • Paste a valid Swagger 2.0 definition that contains both OAuth2 and API Key authentication, such as:

     "securityDefinitions": {
       "oauth2_auth": {
         "type": "oauth2",
         "flow": "accessCode",
         "authorizationUrl": "https://api.xxxx.com/auth/pages/authorize.aspx",
         "tokenUrl": "https://api.xxxx.com/auth/pages/gettoken.aspx?grant_type=authorization_code"
       },
       "api_key": {
         "type": "apiKey",
         "name": "api_key",
         "in": "header"
       }
     },
     "security": [
       { "oauth2_auth": [] },
       { "api_key": [] }
     ]

4. Ensure the swagger file has no validation errors and save the connector.

5. Export the Solution as a Managed Solution → a .zip file is generated.

6. Extract the .zip file and navigate to:
   Connector/connectionparameters.json.

7. Inside the file, locate the type attribute, which incorrectly appears as:

   "type": "oAuthSetting"

8. Expected correct value should be:

   "type": "oauthSetting"

---

Actual Result

The exported solution contains:

"type": "oAuthSetting"

This causes Partner Center validation to fail.

---

Expected Result

The exported solution should contain the correct casing:

"type": "oauthSetting"

This should allow the connector to be published as an OAuth connector in Partner Center without errors.

---

Impact

• Connector cannot be published to Partner Center unless manually corrected.
• Extra steps required for every export.
• Potential confusion for users assuming the connector is not OAuth-compliant.

---

Suggested Fix

Update the export generator to ensure the correct property name:

• Replace oAuthSetting → oauthSetting (lowercase o).