Issue while using Connector for Microsoft Power Platform

[AnupamaJaiswal]

Hi Team,

We are trying – “Connectors for Microsoft Power Platform” from Digital Exchange and facing below issue for which we will need your intervention or help.

While following the attached guides, we are updating the function host keys in “General Information” of Connectors,

Reading from our Azure Function (published as suggested in guides)-

Although during the test call, we are getting Unauthorised Error (404 Response) but the Request URL is displaying some different path, should it not be pointing to above mentioned host URL of Azure function?

URL - https://europe-001.azure-apim.net/apim/blue-20prism-5f95c943ae2f7220d9-5f1a0fbe1f3c371bc5/0c5a34ed213f41409bfb766011c91ba8/api/BluePrismRestInterface?code=PyHWvD18al105dHja9xB7mrrluoGVfhnPUsJuru9MOyP9...

Also, please note we were unable to create/publish the connector with the exact name as displayed in guide- “PowerPlatformConnector”, does it have any dependencies on the name?

Kindly let us know if you would need any input from our end to review this. It would be great if we can connect to understand the blockers here.

 <also attaching the email communication initiated on this thread>

Thanks,

Anupama

[ewilson]

Hi @AnupamaJaiswal,

Regarding your last question, no the function names does not need to match what's shown in the documentation exactly. Since the name you enter results in a URI being created in Azure it must be unique otherwise you run the risk of a name collision if someone posted a public Function App with the same name.

Now, regarding the main issue, when you defined the Custom Connector definition in Power Apps did you edit the resourceName, processName, and code sections?



And on the Security tab of the Custom Connector definition, did you specify anything (ex. Basic Authorization)?


Cheers,
Eric​

[ewilson]

BTW - The URL shown in the test request is based on what region your overall Azure account is tied to. For example, mine is tied to our Blue Prism HQ address in England, so my test request also use a Europe URL even though my Function is tied to a region in the US. Ultimately, Azure straightens it all out on the backend for the test requests. So thos would not be causing your authentication error.

I believe that is tied to you potentially not having the auth code defined for each of the 3 request definitions.

Cheers,
Eric

[AnupamaJaiswal]

Hi Eric,

Thanks for your responses. To answer your below questions-

1. Yes, we have updated the required details in resourceName, code and processName.
2. We did not make any changes in Security tab, but in the Test section we provided BP login details in the connections prompted for username and password. 

We are still stuck with the unauthorized error, please let us know if you have any further insights or would need more details to debug this.

Thanks,
Anupama

[ewilson]

Hi @AnupamaJaiswal,

Ok, so the username and password that you enter on the Connection definition should only apply to the StartProcess action. You should be able to test GetProcessList and GetProcessSchema regardless of the username/password values entered on the connection because those actions are simply scraping the resource PC response you would see if you looked via the browser (ex. http://127.0.0.1:8181/ws/ is the equivalent of the GetProcessList call).​ Can you verify that performing a test of those two actions is successful?
 
Cheers,
Eric

[AnupamaJaiswal]

Hi Eric,

Thanks for your response. 

We tried other two tests and getting the similar 404 response. Please refer the screenshot below-

Appreciate any leads or documentation what we can refer here.

Thanks,
Anupama

[ewilson]

@AnupamaJaiswal,

The resource name doesn't seem quite right. Typically, a runtime resource needs to be addressed with a specific port number (default is 8181). If you open a browser and enter the value of your resourceName entry with "/ws/" appended to the end do you get back a list of the published processes and VBOs?

Example:
http://bnlweafqap20112.s2.xxxxxxxxx.com/ws/

Cheers,
Eric​

[AnupamaJaiswal]

Hi Eric,

When I am opening this link- http://bnlxxxxx0112.s2.ms.xxxxxx.com:8181/ws/ in browser, it is landing to the published processes and VBO's below and giving error without the port number, i.e. - http://bnlxxxxx20112.s2.ms.xxxxxxx.com/ws/

So, added port number as well to resource name in our "Test Operation" call of GetProcessList, and still getting similar 404 error. 

In Summary, have tried with below 3 names in resource name and all gave same error-
a) bnlxxxxxxx20112.s2.ms.xxxxxx.com
b) http://bnlxxxxxxx20112.s2.ms.xxxxxx.com:8181/ ;
c) http://bnlxxxxxxx20112.s2.ms.xxxxxx.com:8181/ws/

Anything else we are missing here? 

[ewilson]

@AnupamaJaiswal,

The value of resourceName ​should just be the resource domain name and port, no HTTP. So it should look like this:

bnlxxxxx0112.s2.ms.xxxxxx.com:8181

Cheers,
Eric

[AnupamaJaiswal]

Hi Eric,

No luck with this one as well-

In this test operation- GetProcessList, there are just two input- 
a) resourceName- bnlxxxxx0112.s2.ms.xxxxxx.com:8181
b) code- we picked from Azure Function Apps- in default key below-

The Azure function and Blue Prism Connector file was picked from Digital Exchange. 

Let us know if you see anything else we can try and test here.

Thanks,
Anupama