Answered

Custom Connector in solutions

(1) Share

Report

Posted on by Den

Hi community!

Question around Customer Connectors and importing solutions to different environments. I have a GraphAPI Custom Connector part of my solution. Whenever I make any update to the PowerApp, export the solution and import to my production environment. The OAuth data is lost on import so the app stops working. I constantly need to come in and re-enter the client id, client secret and resource URL following the import.

Is there anyway around this or anything I'm missing?

Thanks!

Categories:

Connector development

I have the same question (0)

All responses (7)

Answers (1)

Verified answer

PowerPuffKK 316 on at

Like (3)

Report
Copy link

Link copied!

Hi @Den ,

The best way to solve this is by using environment variables.

Add three environment variables to your solution - one for client ID, one for client secret and one for resource URL.

When you then import the solution to your target environment, you'll need to enter those once on import, they are then stored in a Dataverse table. Every subsequent import of an updated solution package will automatically use those variables.

If this answer helps you, please mark it as a solution to help future forum visitors.

Thank you
Kristine 😊

Was this reply helpful? Yes No
Den 11 on at

Like (2)

Report
Copy link

Link copied!

Hi Kristine,

Thank you for your response. I actually didn't realise I could use environmental variables in custom connectors. I have changed my solution to include this now which solves my issue.

If anyone else wants some more info on this: Use environment variables in solution custom connectors (preview) | Microsoft Docs

Many Thanks,
Den

Was this reply helpful? Yes No
sohilbhalla 72 on at

Like (0)

Report
Copy link

Link copied!

Hello @PowerPuffKK , 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

Was this reply helpful? Yes No
sohilbhalla 72 on at

Like (1)

Report
Copy link

Link copied!

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

Left is old, right is new

Was this reply helpful? Yes No
austinm34 10 on at

Like (0)

Report
Copy link

Link copied!

I am having the same issue. We use environment variables for the client ID and secret, and as soon as I export the custom connector solution it clears the client secret variable. I even put it in, resave, and immediately export and it still does the same thing. This is a huge issue because we have sent out new releases to customers without realizing this issue.

Was this reply helpful? Yes No
SimonSays 168 on at

Like (0)

Report
Copy link

Link copied!

This is the one blocker preventing a fully automated CICD pipeline. Would love to know if anybody has found a workaround?

Was this reply helpful? Yes No
SimonSays 168 on at

Like (0)

Report
Copy link

Link copied!
I've devised a workaround that relies on using Azure DevOps for the CICD pipeline. If you don't already have a DevOps pipeline I suggest reading this article first.

I added a folder called Connectors to my Repo and copied the connectionparameters.json file for the custom connector I'd created. Inside this json I add the missing clientSecret e.g
"oAuthSettings": { "identityProvider": "aad", "clientId": "@environmentVariables(\"APIClientID\")", "clientSecret": "@environmentVariables(\"APIClientSecret\")",
then within my pipeline I add a CopyFiles@2 task like this:
- task: CopyFiles@2 displayName: 'Copy Connector Settings Files to: $(Build.SourcesDirectory)/$(SolutionName)/Connectors' inputs: SourceFolder: Connectors Contents: '**' TargetFolder: '$(Build.SourcesDirectory)/$(SolutionName)/Connectors' OverWrite: true
So essentially I'm overwriting the CustomConnectorName_connectionparameters.json file with a file stored in the source control. I only have one custom connector but could apply this for any custom connectors. Hope this helps somebody.

Was this reply helpful? Yes No