[BUG] API-Key setting connection is gone after deploy

[Likkeq]

Type of Connector

Custom Connector

Name of Connector

Microsoft Custom Connector

Describe the bug

We have a custom connector where the security authentication type setting is configured as API-Key. When we redeploy this in a solution to other environment where it already exist it seems that the custom connector is losing the API-Key type configuration.

We tested this by using the Test tab with the existing connection. We get an error that the API-Key is missing. The strange thing is that when going to the security tab the setting is still on API-Key. The workaround to fix this for us is going to edit mode and click on update connector, without modifying anything. We don't modify anything in the existing created connections.

Is this a security bug?

No, this is not a security bug

What is the severity of this bug?

Severity 3 - Minor issue

To Reproduce

• Have a Dynamics environment where the custom connector exist with API-Key setting configured in a managed solution.
• Redeploy a new managed solution version to that environment without any changes of the custom connector.

Expected behavior

API-Key setting is still configured after deploying a new solution version with an existing connection.

Environment summary

Have a dev environment for the unmanaged solution and have a test environment with managed solutions.

Additional context

• Because we need to manual update the custom connector everytime we have now seperated the custom connector in a seperate solution that we manually export and import if there is a change. Putting it in our devops pipeline causing too many issue of constant manually updating.

[troystaylor]

Could you download the connector using the pac CLI from the other environment and check to see if the apiProperties.json file has the API key connection parameter?:

[Likkeq]

Yes, downloaded it and it has the API-Key properties.