cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Highlighted
Stevel
Level: Powered On

Custom Connector Authorization URL includes parameter - fails

Hi all,

 

I'm attempting to build my first Flow or PowerApps custom connector to a RESTful service provided by our medical records system vendor. The vendor is following new healthcare industry standards for RESTful APIs called Fast Healthcare Interoperability Resources, FHIR.

 

Using Postman, I can call the FHIR API and get appropriate results, so I created a collection per the PA advice:

https://powerapps.microsoft.com/en-us/tutorials/register-custom-api/ 

 

When creating the custom connector however, I'm asked to provide the Authorization URL and the one I've been given to use includes a parameter: https://oauthtest.netsmartcloud.com/authorize?sdk_scope=MHCD!SBOX:QA which they use to route my call to the correct development environment.

 

The PA Custom connector wizard converts this into an invalid token request URL because it adds other items behind it's own question mark.

 

This is from the wizard token request:

https://oauthtest.netsmartcloud.com/authorize?sdk_scope=MHCD!SBOX:QA?client_id=1111111111111111111111111111111&response_type=code&redirect_uri=https%3a%2f%2fmsmanaged-na.consent.azure-apim.net%2fredirect&scope=Patient&state=11111111111111111111111111111111111111  (<== the client_id and state shown here are fake of course)

 

So, the token request fails and I'm unable to use the custom connection in my apps.

 

Are there any known work arounds for this issue?

 

Thanks!

...Steve

1 REPLY 1
Community Support Team
Community Support Team

Re: Custom Connector Authorization URL includes parameter - fails

Hi Stevel,

 

I assume that this documentation on “Register and use custom connectors in PowerApps” could be your reference, please check it at here:
https://powerapps.microsoft.com/en-us/tutorials/register-custom-api/

 

From the doc we know that when using a Postman Collection, authentication type is auto-populated only when using supported authentication types, such as OAuth 2.0 or Basic. What’s the type on your side? Please make sure you are using supported authentication types.

 

More details about how to describe a custom connector with Postman, please see this doc at here:
https://powerapps.microsoft.com/en-us/tutorials/postman-collection/


Best regards,
Mabel Mao

Community Support Team _ Mabel Mao
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.