[Microsoft Customer Power Platform Custom Connectors PRODUCT FEEDBACK] #121
Description
Submitted By
Your Role
I am a Software Developer
What is your role in this learning context?
- Professional Developer
For Product
I have feedback on
- A Microsoft Topic
Specify a name and share a link to the learning resource you were using
Description
Example 1: Seeking clarification: Clear examples of usage of scopes on creation of custom connectors on Power Platform_.
Details
(Use this section to provide more details on the feedback if possible)
Example 1: Scope Clarification:
For the 30 days of learning, I was working on Wakatime Api as my proposal for power platform connector. The API is well documented on the side of the Wakatime however I encountered a problem within the steps on Power Automate.
Here is a breakdown of the related issue that I encountered.
--
- I created the API from scratch from the custom connectors tab
- Added the details as required on the steps to creating the API.
- I created a new app on the Wakatime dashboard as required so that I can get the client Id and also the client secret to be used on the app
- On the security tab I added authentication for the API and choose Oauth 2.0 for my authentication. The steps involved here included adding the client ID, client Secret, Authorization URL, token URL, refresh URL and scope.
The whole process went seamless until the bit of scope.
- My Api has about 6 scopes that should be added and use comma to separate the scopes. I tried adding comma to separate them but got an error that it is not a valid scope. I also tried working with one scope and it worked perfectly.
From the online documentation and materials, I did not quite find one that clearly states how the scopes should be added into the security tab and at least an example of how to separate them using a comma.
I went ahead and tried editing them on Swagger, but the changes did not reflect
- However some of the endpoints of the API that do not require authorization work perfectly when I do a test