Custom connector issues after exporting solution to new environment

(1) Share

Report

Posted on by Svenny

153

Hello,

I am having some issues with a custom connector after exporting this through a solution from our dev environment to our test environment.

According to the documentation, a custom connector should be created through a solution and exported independently and before other components.

After exporting the solution containing only the connector and configuring the connector in the test environment, the connector is working fine.

We then export the main solution containing the connector and other components to the same test environment. It then appears we have to reconfigure the connector after this import.

The last step of importing the main solution appears to break the custom connector. The connector is being used together with a custom page. After successfully creating a connection to the custom connector in the environment, testing returns 401 for the operations we attempt in the connector test tab.

Any ideas on what we are doing wrong?

Categories:

Connector development

I have the same question (0)

All responses (7)

Answers (2)

CeoxSteve 16 on at

Like (1)

Report

I don't think you are doing anything wrong, there is something fundamentally broken with custom connectors and deployment where the custom connector seems to break after deployment.

I have seen people post that if you use oath with environment variables it seems to work correctly (going to be trying this shortly). I'm using key based authentication and always had the same behaviour you are seeing.

Was this reply helpful? Yes No
DenysNozhenko 10 on at

Like (1)

Report

same problem, had to create a new custom connector and change every single action in my flow
I love Microsoft

Was this reply helpful? Yes No
Verified answer

Svenny 153 on at

Like (1)

Report

A small update on this. We had to create pipelines for our solutions in order to work around these issues. When deploying using a pipeline we do not get this error anymore.

Was this reply helpful? Yes No
DenysNozhenko 10 on at

Like (0)

Report

What kind of pipelines did you use?

Was this reply helpful? Yes No
Verified answer

SurfaceWear 186 on at

Like (3)

Report

It's good that you solved this using Pipelines however this is not an appropriate solution since this comes with additional license costs to get access to Pipelines.
Core functionality should be supported through the standard (manual) solution import method, and clearly it is not.
Our workaround is to import the custom connectors in their own solution and not include them in any dependent solutions. After the initial import of the connector solution, we make a minor change to each connector (e.g. the colour), save, and then they work. However - this is a workaround, not a solution!

Was this reply helpful? Yes No
sohilbhalla 72 on at

Like (0)

Report

I am also facing the same issue. I am using environment variables for my client id and secret which in turn connects to Azure Key Vault. But when I import the solution in the environment it seems the client secret is getting cleared inside the custom connector. I am using client secret as @environmentVariables("clpr_ClientSecret") inside my connector.

Then I have to edit the connector manually in the solution in the target environment and put the client secret again as @environmentVariables("clpr_ClientSecret"), which solves the problem, but it turns my solution from managed to unmanaged solution( which is a bigger problem).

Not sure what can be done here? this does not seem to be desired behavior

In my export of the solution the connector connection parameters file is missing client secret. This has been changed recently may be with new powerapps client version as in my previous solutions i can see client secret as well-

{
  "token": {
  "type": "oauthSetting",
  "oAuthSettings": {
  "identityProvider": "oauth2",
  "clientId": "@environmentVariables(\"clpr_ClientID\")",
  "scopes": [],
  "redirectMode": "GlobalPerConnector",
  "redirectUrl": "https://global.consent.azure-apim.net/redirect/clpr-5fpowerrentalconnector-5f170d5cb93436007c",
  "properties": {
  "IsFirstParty": "False",
  "IsOnbehalfofLoginSupported": false
},
  "customParameters": {
  "AuthorizationUrl": {
  "value": "https://login.microsoftonline.com/<tenantid>/oauth2/authorize"
},
  "TokenUrl": {
  "value": "https://login.microsoftonline.com/<tenantid>/oauth2/token"
},
  "RefreshUrl": {
  "value": "https://login.microsoftonline.com/<tenantid>/oauth2/token"
}
}
}
}
}

These are differences

Was this reply helpful? Yes No
chajdub 2 on at

Like (0)

Report

me2

coomapak.pdf

Was this reply helpful? Yes No