microsoft/powerplatformconnectors

This is a repository for Microsoft Power Automate, Power Apps, and Azure Logic Apps connectors

powerplatformconnectors's Issues

paconn validate command gets service error when swagger contains invalid $ref values

Describe the bug
When a swagger file (apiDefinition.swagger.json) contains invalid $ref values, they should be reported as errors by the paconn validate command.

To Reproduce

1. cd into the following folder: certified-connectors\Pushcut
2. run: paconn validate -d apiDefinition.swagger.json
3. Note, the command executes and displays a couple warnings. This is the success case.
4. Open the file: apiDefinition.swagger.json
5. Modify the first "$ref" property by making it invalid:
   e.g. "$ref": "#/definitions/NotificationZZZZ"
6. run: paconn validate -d apiDefinition.swagger.json

The last command reports a service error response like:

{
  "error": {
    "code": "InternalServerError",
    "message": "Encountered internal server error. The tracking Id is '61e92b1e-25b0-474d-8aa2-5be81dc9ea7f'."
  }
}
500 Server Error: Internal Server Error for url: https://api.powerapps.com/providers/Microsoft.PowerApps/objectIds/adce0039-9545-4253-ae21-0cb17e131cd8/validateApiSwagger?api-version=2016-11-01&enableConnectorCertificationRules=true

Expected behavior
Invalid $ref values should result in this command reporting them as errors.
Preferably, reporting multiple ref errors if the file contains them.

Buffer Connector stopped working - HTTP 403

Describe the bug
The Buffer connector is unable to read the profile json via API.

There might have been a breaking change between 16h and 17th of September on the Buffer API.

To Reproduce
Create a Buffer connector, authorize with your account and add the connector to a Flow.

Expected behavior
The list of configured profiles in Buffer would be listed and messages from Power Apps should be queued by Buffer.

Additional context
This Buffer Connector was created by Microsoft, as stated in the documentation (https://docs.microsoft.com/en-us/connectors/buffer/) but is not source controlled in this Repo!!!

[paconn] Paconn Update Throws Error

Describe the bug
Recently (in the last 3 days) i am getting a weird error when trying to update the connectors via paconn-cli. Issue exists on both Mac OS and Linux Platform

Expecting value: line 1 column 1 (char 0)
Traceback (most recent call last):
  File "/projects/.venv/lib/python3.6/site-packages/knack/cli.py", line 206, in invoke
    cmd_result = self.invocation.execute(args)
  File "/projects/.venv/lib/python3.6/site-packages/knack/invocation.py", line 188, in execute
    cmd_result = parsed_args.func(params)

  File "/projects/freelancing/azure-app/azure-fn-msflow-agent/plangrid-agent/swagger/fp/shared_plangrid-20-5fa1c41dcf6720de46-5f986c0f1bdfc46983/.venv/lib/python3.6/site-packages/paconn/apimanager/apimanager.py", line 115, in request
    response_content = json.loads(response.content)
  File "/usr/lib/python3.6/json/__init__.py", line 354, in loads
    return _default_decoder.decode(s)
  File "/usr/lib/python3.6/json/decoder.py", line 339, in decode
    obj, end = self.raw_decode(s, idx=_w(s, 0).end())
  File "/usr/lib/python3.6/json/decoder.py", line 357, in raw_decode
    raise JSONDecodeError("Expecting value", s, err.value) from None
json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)

To Reproduce
Download any Connector using Paconn download and just try to update back using paconn update -s settings.json

Expected behavior
A clear and concise description of what you expected to happen.

Environment summary
Installed using pip install

On Linux
paconn --version
0.0.13

Python (Linux) 3.6.9 (default, Apr 18 2020, 01:56:04)
[GCC 8.4.0]

On Mac
0.0.13

Python (Darwin) 3.7.7 (default, Mar 21 2020, 14:41:45)
[Clang 9.0.0 (clang-900.0.39.2)]

Additional context

Add Canvas App Export Feature

I would really like the ability to export apps pragmatically and move then to different environments. I feel like most people, that are using PowerApps as fast deployed solutions, have a Dev Environment and a Prod Environment.

If you could export the app and then import the app in a new environment I feel like this would solve the problem.

You also could just add functionality to copy it to a different environment, but it might be easier/more flexible to just allow exporting and importing apps

Additional context
https://docs.microsoft.com/en-us/power-platform/admin/environment-and-tenant-migration

Schema Validation Error

When run check for validation using, paconn validate --api-def [Location of apiDefinition.swagger.json] command, schema validation errors are coming even though the file is in working condition.

The PR is here

git push: refusing to allow an OAuth App to create or update workflow `.github/workflows/validation.yml` without `workflow` scope

Describe the bug
When I try to push the latest changes from this repository to my fork I receive output as follows:
Total 0 (delta 0), reused 0 (delta 0)
To https://github.com/IvanBil/PowerPlatformConnectors
! [remote rejected] master -> master (refusing to allow an OAuth App to create or update workflow .github/workflows/validation.yml without workflow scope)
error: failed to push some refs to 'https://github.com/IvanBil/PowerPlatformConnectors'

To Reproduce

git fetch upstream

git checkout master

git merge upstream/master

git push

Expected behavior

The push completes successfully like it was a few months ago.

Environment summary
Powershell with Git for Windows, Windows 10 Professional

Localization of Custom Connectors

We would like to distribute a custom connector in a solution with multiple languages (primarily labels, descriptions etc.) - how can we include translations with the Swagger definition?

Reference #274

Normalize casing of policy template instances

Currently, policyTemplateInstances have different cases for different connectors.

In reality, the RPs are not case-sensitive on these ids. Yet normalizing on a casing would simplify schemas and checked in code.

To address this, we'd need to:

• normalize existing instances in the repo
• update paconn to do this normalization so it doesn't need to be done manually.

Originally posted by @mamurshe in https://github.com/microsoft/PowerPlatformConnectors/diffs

paconn and PR validation should not save clientId values, and ensure they aren't added in PRs

We should:

1. ensure paconn doesn't automatically save clientIds
2. PR process should validate that clientIds are not checked into the repo.
3. paconn tool should be designed to allow a developer to provide the clientId (it already provides the clientSecret as a parameter).

Originally posted by @mamurshe in #199

Connect with service principal

Is your feature request related to a problem? Please describe.
Custom connector should provide an option to connect with service principal credentials.

Describe the solution you'd like
Like other standard connectors provides option to connect with service principal credentials.

Describe alternatives you've considered
Already tried in swagger editor to change flow from accessCode to application. After Update connector action oauth2 flow is changed back to accessCode.

Sample yaml:

securityDefinitions:
  oauth2_auth:
    type: oauth2
    flow: application 
    tokenUrl: https://login.microsoftonline.com/common/oauth2/token

Additional context
Custom connector should provide connectivity without user context (aka service-to-service communication) and application permission (not delegated).

No token to access

This issue occurs when running the flow after using FacebookCustomConnector.

The error message.
{"error":{"message":"(#200) If posting to a group, requires app being installed in the group, and \\n either publish_to_groups permission with user token, or both manage_pages \\n and publish_pages permission with page token; If posting to a page, \\n requires both manage_pages and publish_pages as an admin with \\n sufficient administrative permission","type":"OAuthException","code":200,"fbtrace_id":"AzXqcby3Z7R72M88cOfZ7ED"}}

I found that there's no Get my Access Token option when using the connector and it should be the root cause.

Can you suggest how I can modify the json file to make it work?

InvalidRequestContent: Could not find member 'stackOwner' on object of type 'ApiPropertiesDefinition'

Describe the bug
I cannot create a new connector based on any of the certified connectors in this repository, as it always reports back the following response:

{
  "error": {
    "code": "InvalidRequestContent",
    "message": "The request content was invalid and could not be deserialized: 'Could not find member 'stackOwner' on object of type 'ApiPropertiesDefinition'. Path 'properties.stackOwner', line 1, position 1161.'."
  }
}

To Reproduce
Go into certified-connectors/Connective eSignatures, and run:

paconn create

Expected behavior
New connector to be created in my environment.

Additional context
It works when I remove stackOwner property from the apiProperties.json file. That's annoying because I'd need to remember to add it back in to submit an update to the connector.

Issue in documentation of Planner Connector

Hi Team,

We have followed Document and now able to building the connector and found where the issue is present .

It was mentioned in the above Document which was incorrect,

For API permissions, among other required permissions under "Microsoft Graph", please make sure "User.Read" is added. "User.Read" permission is required in order to login the current user and retrieve relevant information.

Solution(Document need to be updated)

We need to have any one of Group.Read.All, Group.ReadWrite.All permission and grant permission for APP to use planner as per MS Document

When bundling custom connector image with solution, the image is replaced with the default one

When the iconblob is set to a valid PNG file, the default custom connector icon is still used.

The image is bundled in the solution ZIP file and customizations.xml contain the XML below which has correct paths as well:

<?xml version="1.0" encoding="utf-8"?>
<Connector xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <connectorid>59918c08-cc28-44b4-bf4f-edb5365517fd</connectorid>
  <description></description>
  <displayname>TALXIS_Connectors_XXXX</displayname>
  <iconbrandcolor>#007ee5</iconbrandcolor>
  <name>talxis_connectorsxxxx</name>
  <connectortype>1</connectortype>
  <openapidefinition>/Connector/talxis_xxxx_openapidefinition.json</openapidefinition>
  <connectionparameters>/Connector/talxis_xxxx_connectionparameters.json</connectionparameters>
  <policytemplateinstances>/Connector/talxis_xxxx_policytemplateinstances.json</policytemplateinstances>
  <iconblob>/Connector/talxis_xxxx_iconblob.png</iconblob>
</Connector>

[paconn] Add support for logout

Problem:
Sometimes we use a different accounts to deploy a connector across different environments (a PROD/TEST environment vs a community environment). The paconn utility, once logged in, cannot be used to target the other environment. The only option seems to wait out until the token expires - which is extremely painful.

Describe the solution you'd like
Add a paconn logout command.

Describe alternatives you've considered
Another window/session.

paconn does not have logout

Is your feature request related to a problem? Please describe.
If you login to paconn with account A and then want to login to paconn with account B there is actually no way to do this. Running paconn login again tells you you are already logged in. Running paconn logout does not exist as a command

Describe the solution you'd like
Add paconn logout or allow paconn login to be run while you are already logged in

Please add swagger validation exception for error code 202

PR - https://github.com/microsoft/PowerPlatformConnectors/pull/439/checks?check_run_id=1102525157

Swagger validation is failed when partner is added an error code for '202' code. Can you please provide let us know why it is not supported.

can you please add it to swagger validation exceptions as Partner is receiving 202 for some operations of their API.

Facebook connector - 404

Hi,

I try to deploy the facebook sample custom connector with no success.

• I registered a facebook app, with product "Facebook login" and I marked it as "native app".
• On the apiProperty.json file I updated the clientID.
• with the paconn I registered the connector on my tenant using the commands
  paconn login
  paconn create -s [Path to settings.json] --secret [The OAuth2 client secret for the connector]

No error shows untill this point, but accessing the custom connector I the 404 page with this message
"Error: Failed to retrieve api with http status code 'ApiResourceNotFound' and error message 'Could not find api ..."

Any suggestions will be appreciated
Thanks

Rename paconn settings.json file to something less generic

Is your feature request related to a problem? Please describe.
settings.json is too generic a name for tooling. e.g. /.vscode/settings.json. This file is owned by vscode, but because it's in a subfolder it's unambiguous.

Furthermore, writing VS Code tooling to this file would be simpler if it had a unique name.

Also, we can add a more specific filename to our .gitignore to prevent this file (a user-specific) file from accidentally being added to the repo.

Describe the solution you'd like
how about paconn-settings.json?
all lowercase and usage of '-' allows for easy normalization of the filename.

CSRF Token Validation Failed

Describe the bug
I am connecting to SAP Demo System using Power Automate and OData connector. I am able to fetch the products successfully but while adding product I am getting error : CSRF Token validation failed.
To Reproduce
Steps to reproduce the behavior.
Step 1: I am creating a flow manual start action (for testing purpose, using power apps action also gives same error).
Step 1 : Add ListProuctSet action
Step 3 : Add product set action with set cookies and headers like this : replace(outputs('List_product_sets')?['headers/Set-Cookie'],',',';')
Step 4: run flow
Expected behavior
It should add new product in SAP system

"On all new alerts" trigger fires continuously

Describe the bug
I created a very simple flow with the "On all new alerts" trigger. Unfortunately, the trigger fires every 2 minutes and outputs the same 20 alerts.

To Reproduce
Create a flow with the "On all new alerts" trigger. Watch what happens.

Expected behavior
The flow should run only when there are new alerts, and it should never run on the same alert more than once.

Environment summary
Microsoft Flow

Additional context
Screenshot of flow:

Validate function does not recognize allowable number formats such as int64

Describe the bug
If the api definition file contains definition with properties of type "number", with format "int64", the validation function throws the following error:

The type/format 'number/int64' is not recognized.

This is inconsistent with the OpenAPI 2.0 specification, which, in addition to an empty value, allows the following format values for type "number":

float
double
int32
int64

To Reproduce
Create a definition similar to the following:

"customDefinition" : {
"type" : "object",
"properties" : {
"prop1" : {
"type" : "number",
"format" : "int64",
"description" : "Property 1"
}
}

Run paconn validate --api-def apiDefinition.swagger.json

Command returns "definitions/customDefinition/properties/prop1/format: The type/format 'number/int64' is not recognized".

Expected behavior
The definition should pass validation.

Environment summary
Install Method: pip
CLI Version: 0.0.14 (Python 3.8.3)
OS: Mac OS 10.15.5

Array name gets put before field name/renaming arrays in custom connector

Hello,
I have been creating a custom connector and I came upon an issue. When I define an array, custom connector automatically names fields after that array, which creates mess and is basically unusable/unreadable.
Example of OpenApi definition:

And how it looks in the custom connector:

As you can see, name of the array (People) is put before every single field. And when another array is defined (positions), it get put there too, making even more mess.
Any suggestion on how to fix this?

400 Client Error: Missing Object ID

Describe the bug
Following Microsoft/PowerPlatformConnectors/AzureKeyVault Recipe

Created new AppRegistration as per step-by-step guide in docs.microsoft.com referenced on the github article, added the permissions
Downloaded the two JSON files, the api definitions and the api properties, modified the data inside to match the clicks I made on my side.
As per the recipe I run this command to create:

paconn create --api-def apiDefinition.swagger.json --api-prop apiProperties.json --secret "Foo********Bar"

and I get this error.
Please select an environment:
[1] Default Environment
Environment selected: Default Environment
{
"error": {
"code": "MissingObjectId",
"message": "The provided object identifier was null or missing."
}
}
400 Client Error: Bad Request for url: https://api.powerapps.com/providers/Microsoft.PowerApps/objectIds/validateApiSwagger?api-version=2016-11-01
The same error happens when I try and validate with the command below
paconn validate --api-def apiDefinition.swagger.json

Line 3 of teh apidefinition.swagger.json file looked suspicious considering i'm getting an object message.

{
  "basePath": "/",
  "consumes": [],

&& to triple check I pasted the file in an online json formatter and it confirmed it was a valid format.. so it's not a typo...
I read over the docs to make sure I didn't miss a click in portal.azure; and my user eyes say followed each step and started over a few times.
Frustrating to be hung up on the equivalent to Hello World -> your help and time is greatly appreciated!!!!

Cheers,
~C

Bundling Custom Connectors with Solutions and apiProperties.json

We want to ship all our connectors in solutions, since it appears to be the right approach to us (versioning, deployments etc.). We authenticate our connectors with Azure AD. In order for the connector to work correctly, we need to provide both Client ID and Client Secret. Client ID is a public information, and it's fine to have it inside a solution, but with Client Secret, it's a bit tricky. Generally, I don't want it bundled in the solution, but in order for import and connector to work post import, I need to include the ClientSecret which paconn does behind the scenes on import.

Since Azure AD supports certificate based authentication, wouldn't there be a way to enable a certificate based authentication where certificate is held only by MS and I set the public key as trusted to my app? It would be much more secure and would prevent shipping secret in the solution.

I noticed that MS first party connectors have something like dynamicscrmonlinecertificate:

or office365usercertificate:

I really would prefer to use this sort of authentication. Isn't there some sort of generic certificate and provider which can be used?

paconn tool does not have a way to create zip file, even though instructions say to do this

Describe the bug
The instructions in the connector certification portal say: "Please use the CLI Tool to create the zip file containing your connector artifacts. Documentation on this process can be found here."

However, this is not possible because paconn has no way of outputting a zip file

Expected behavior
Provide paconn package command that outputs a zip file. Right now paconn download makes a folder, but not a zip file. The website actually requires a zip file.

Can't use 'paconn update'

Describe the bug
paconn update never succeeds for me. Running with a debug flag to show that the application spends minutes on this line urllib3.connectionpool : Starting new HTTPS connection (1): api.powerapps.com:443 before returning with error.

urllib3.connectionpool : Starting new HTTPS connection (1): api.powerapps.com:443
urllib3.connectionpool : https://api.powerapps.com:443 "PATCH /providers/Microsoft.PowerApps/apis/abc?api-version=2016-11-01&%24filter=environment%20eq%20%27Default-xyz%27 HTTP/1.1" 502 0
Expecting value: line 1 column 1 (char 0)
Traceback (most recent call last):
  File "/usr/local/lib/python3.7/site-packages/knack/cli.py", line 206, in invoke
    cmd_result = self.invocation.execute(args)
  File "/usr/local/lib/python3.7/site-packages/knack/invocation.py", line 188, in execute
    cmd_result = parsed_args.func(params)
  File "/usr/local/lib/python3.7/site-packages/knack/commands.py", line 131, in __call__
    return self.handler(*args, **kwargs)
  File "/usr/local/lib/python3.7/site-packages/knack/commands.py", line 238, in _command_handler
    result = op(client, **command_args) if client else op(**command_args)
  File "/usr/local/lib/python3.7/site-packages/paconn/commands/update.py", line 51, in update
    overwrite_settings=False)
  File "/usr/local/lib/python3.7/site-packages/paconn/operations/upsert.py", line 135, in upsert
    payload=property_definition)
  File "/usr/local/lib/python3.7/site-packages/paconn/apimanager/powerappsrp.py", line 71, in update_connector
    payload=payload)
  File "/usr/local/lib/python3.7/site-packages/paconn/apimanager/apimanager.py", line 115, in request
    response_content = json.loads(response.content)
  File "/usr/local/Cellar/python/3.7.7/Frameworks/Python.framework/Versions/3.7/lib/python3.7/json/__init__.py", line 348, in loads
    return _default_decoder.decode(s)
  File "/usr/local/Cellar/python/3.7.7/Frameworks/Python.framework/Versions/3.7/lib/python3.7/json/decoder.py", line 337, in decode
    obj, end = self.raw_decode(s, idx=_w(s, 0).end())
  File "/usr/local/Cellar/python/3.7.7/Frameworks/Python.framework/Versions/3.7/lib/python3.7/json/decoder.py", line 355, in raw_decode
    raise JSONDecodeError("Expecting value", s, err.value) from None
json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)

To Reproduce
I've download my settings with paconn download and then executed with paconn update --settings settings.json --debug
Expected behavior
I expect that the API definition is updated and without errors.

Environment summary

paconn --version
0.0.13

Python (Darwin) 3.7.7 (default, Mar 10 2020, 15:43:33)
[Clang 11.0.0 (clang-1100.0.33.17)]

Python location '/usr/local/opt/python/bin/python3.7'

macOS. paconn instaled using pip.

[paconn] simplify paconn create/update commands so filenames are assumed to be the expected folder layout filenames

Describe the bug
The names of these files should be assumed if not specified. The filenames already have defaults in the settings.py file. We shoudn't have to specify them on the cmd line or explicitly in the settings.json file. Instead, they should use the same default values.

While the repro steps describe one of the ways this behavior shows up, the ask here is to make it so that adherence to the folder structure and filenames results in simpler command execution.

To Reproduce

1. cd into an existing connector's folder (e.g. certified-connectors\AzureAD)
2. create a settings.json file with the following content:

{
  "connectorId": "myAzureAD"
}

3. run the command paconn create -s settings.json
   a. When prompted, select an environment and hit enter.

Expected behavior
A custom connector should've been created successfully.

Actual Behavior
An error occurs stating: API Properties must be specified.

Looks like you changed the folder structure, which broke links In Power Automate documentation

Describe the bug
Broken links in Power Automate docs due to folder changes in this repo.

To Reproduce
Click on links references this repo on this page - https://docs.microsoft.com/en-us/connectors/facebook/

Expected behavior
You may want to check with Docs team to figure out how impactful this is across all Power Platform docs.

Environment summary
Install Method (e.g. pip, interactive script, apt-get, Docker, MSI, edge build) / CLI version (paconn --version) / OS version / Shell Type (e.g. bash, cmd.exe, Bash on Windows)

Additional context
Add any other context about the problem here.

Swagger for Facebook Connector Has Errors

Describe the bug
Unable to create a power automate app with power platform Customer facebook connection.

To Reproduce

1. Go to power automate.
2. Go to Data--> Custom connections tab.
3. Click on new custom connectors icon.
4. Click on Import an OpenAPI file.
5. Select apiDefinition.swagger.json file within "..\Custom Connection\PowerPlatformConnectors-master\custom-connectors\Facebook".
6. Put client id and client secret.
7. Click on create connector.

Expected behavior
Specified swagger has the following errors: 'Definition is not valid. Error: 'Error : paths/~1{pageId}~1feed/get/parameters/0/x-ms-dynamic-values/parameters/Accept : The parameter could not be found in operation 'GetMyPages' in the swagger document. ## Error : paths/~1{pageId}~1feed/post/parameters/0/x-ms-dynamic-values/parameters/Accept : The parameter could not be found in operation 'GetMyPages' in the swagger document. '

There is any way to login without the need to access a endpoint?

Description of Feature or Work Requested
There is a CLI tool, but to log in, we need to access an endpoint through a browser. No problem with that, it works, but this blocks things like continuous delivery where we expect to log in through the terminal in a CI environment.

There is any way to do that or if not, there is any plan to implement this feature?

Swagger Validator doesn't allow UTF-8 encoding swaggers

Describe the bug
Swagger Validator doesn't allow UTF-8 encoding swaggers. Please allow all the possible encodings.

Swagger error using Facebook connector

Describe the bug
When using the Facebook connector, I get a swagger error.

To Reproduce
-Create a Facebook custom connector on Power Automate.
-Import the apiDefinition.Swagger.json
-Create the connector

Expected behavior
The connector is expected to be created successfully

Environment summary

Additional context
Error message:
_Specified swagger has the following errors: 'Error : paths/~1{pageId}~1feed/get/parameters/0/x-ms-dynamic-values/parameters/Accept : The parameter could not be found in operation 'GetMyPages' in the swagger document.

Error : paths/~1{pageId}~1feed/post/parameters/0/x-ms-dynamic-values/parameters/Accept : The parameter could not be found in operation 'GetMyPages' in the swagger document.__

Can we please add a Readme.md file for the samples?

The samples "CompaniesHouse" and "IdealPostcodes" looks interesting, but I dont know how to get started. Can we please add a ReadMe.md file with instructions?

Ideally the ReadMe will target both contributors and end users and will contain the following:
[1] A brief intro on the service/API we are connecting to - so that users understand what the connector is supposed to do. For contributors, the link to the API descriptions will be helpful.
[2] Any requirements to create the connector - like an OAUTH App registration, if required.
[3] A brief description of the functions/operations exposed by the connector.
[4] A brief description on how to use the connector - how to sign up, get keys, etc.

Support client credentials Oauth 2.0 flow

At the moment, it seems that only the accessCode flow is supported in the generic Oauth 2.0 identity provider. However, our APIs use the authorization code flow and client credentials flow. Which makes an integration with Microsoft Power Automate impossible for us unless we change our Oauth 2.0 implementation.

When I try to create a custom connector forcing the client credentials flow using the "application" as flow. It gets uploaded with the CLI but then when I try to make a connection with my connector, it fails saying it is missing an "authorizationUrl", which makes me think it falls back to accessCode all the time.

Custom connectors should ideally be allowed to chose at least the client credentials flow and not just the accessCode flow.

paconn validate (Bad Request for url)

Describe the bug
When attempting to validate a connector you get the below error

Navigating to the URL given in the error

https://api.powerapps.com/providers/Microsoft.PowerApps/objectIds/c03fcc17-7e4e-4a4a-bf0f-5f39e2844a83/validateApiSwagger?api-version=2016-11-01&enableConnectorCertificationRules=true

returns

{"message":"No HTTP resource was found that matches the request URI 'https://api.powerapps.com/providers/Microsoft.PowerApps/objectIds/c03fcc17-7e4e-4a4a-bf0f-5f39e2844a83/validateApiSwagger?api-version=2016-11-01&enableConnectorCertificationRules=true'."}

To Reproduce
paconn validate --api-def apiDefinition.swagger.json

Expected behavior
A clear and concise description of what you expected to happen.

Environment summary
paconn-cli version 0.0.10 running in Docker container on MacOS Mojave

docker run --rm -it -v $(pwd):/usr/app/paconn garryt/paconn-cli

Update readme.md with instructions for merging and submitting PR's

The instructions for submitting a connector to the repo terminate at getting the local dev environment configured. There are no steps provided for how to proceed beyond copying connector artifacts into a subdirectory. This is confusing for people who do not use Git on a regular basis. A generic statements such as "Updates to certified connectors must first be made through a pull request to the dev branch for review by the connector owner" does not provide enough information to complete the process.

Since final certification and deployment is dependent on this task, it is imperative that clear instructions be given on how to properly merge a dev branch and submit a PR to maximize the possibility of acceptance. As with the previous section on creating a fork, the certified connectors section should provide sample commands and sequential steps. There are too many ways to accomplish a task in Git to leave it at generic, open-ended statements.

[paconn] Allow client credentials authentication

Use case
As a developer, I want to be able to run paconn from inside my DevOps pipelines. For that, I need to use an AAD Service Principal for authentication, allowing for paconn to run with no user interaction in a transient environment (e.g.: a short-lived Docker container).

Additional context
As of today, paconn only supports device authentication, which requires user interaction - subsequent operations won't prompt for login, but then it requires a persistent environment for caching the token. Support for client credentials authentication would allow running paconn with no user interaction, making it possible to use it in several DevOps solutions (e.g.: ADO, Github Actions, Jenkins, Bamboo and so on).

How it could work
By having an additional --client_secret flag on login command, we could switch from device authentication to client credentials authentication. In profile.py we could have an additional function, such as:

    def authenticate_client_credentials(self):
        """
        Do some stuff ...
        """
        mgmt_token = context.acquire_token_with_client_credentials(
            resource=self.resource,
            client_id=self.client_id,
            client_secret=self.client_secret)

        """
        Do some more stuff ...
        """

        return credentials.token

And, in auth.py:

        if profile.client_secret:
            credentials = profile.authenticate_client_credentials()
        else:
            credentials = profile.authenticate_device_code()

Localization of custom connector

I didn't find any document about the localization for custom connector, but I do see that the certified connector is localized if I change the PowerAutomate page to a different language, how it happened? it's auto translated by Bing translator?

Not clear instructions for creating Facebook App especially requesting permissions

Hi,
after creating the custom connector i am facing errors in the actions, especially "post message to page" which requires extra permissions on the Facebook App check attached screenshot.

or am I doing it in a wrong way?

[paconn download] apiProperties.json should not emit internal properties

Describe the bug
When downloading the connection parameters for a connector, certain properties of the oAuthSettings object should not be saved, as these are output properties, not input properties.

To Reproduce
paconn download for any connector that uses oauthsettings tokens.

Expected behavior
the following properties under the oAuthSettings object should not be saved:

• redirectUrl
• properties - This is an object which has only internal, client values. e.g. '/properties/IsFirstParty'

PROJECT777

Client Certificate authentication in Custom Connector

We need to connect to a custom API through a proxy server thats need a client certificate for authentication. Also, the custom API it self needs Oauth 2 for handling the authentication.

So we have to types of authentication for 1 HTTP request.

Custom connectors do not support client certification at all and you are only able to choose 1 type of authentication.

Describe the solution you'd like
Maybe APIM Policy's for adding a client certificate? Like this: https://docs.microsoft.com/nl-nl/azure/api-management/api-management-authentication-policies#ClientCertificate

Describe alternatives you've considered
Normal HTTP request support client certificates, but then we need to manually do the oauth process which is not 100% secure.

Microsoft MVP API

Describe the bug

I have a custom connector for Microsoft MVP API.
https://github.com/johnnliu/flow/blob/master/MVP%20Production.swagger.json

The API needs two pieces of authentication.

MSA and a per-user Ocp-Apim-Subscription-Key.

I'm not sure how to write a custom connector that has two authentication parts. Also, the API header is needed in every call.

Would love to pull it into this project, but there's an issue with it and I'm not sure how to write this swagger. Right now, people that used this had to take a copy and override line 35.

[paconn-cli] Cannot import name 'BlockBlobService' from 'azure.storage.blob'

Description of Feature or Work Requested
When calling the 'update' command with a fresh install of the paconn tool, the following error occurs:

Cannot import name 'BlockBlobService' from 'azure.storage.blob'

It turns out the latest version of the azure.storage.blob package (v12.1.0) has breaking change compared to the previous version (v2.1.0). And it doesn't have the BlockBlobService anymore.

Update the readme.md with a section about VS Code integration

Can you please update the readme.md and add a section about VS Code and how to use the schema?

Originally posted by @mamurshe in #163 (comment)

Logout does not work

Describe the bug
Logout does not work

To Reproduce
paconn logout

Expected behavior
logout from existing env

Environment summary
c:\Users\daemel\Downloads\Code\repos>paconn --version
0.0.13

Python (Windows) 3.8.2 (tags/v3.8.2:7b3ab59, Feb 25 2020, 23:03:10) [MSC v.1916 64 bit (AMD64)]

Python location 'c:\users*****l\appdata\local\programs\python\python38\python.exe'

Additional context
c:\Users\daemel\Downloads\Code\repos>paconn logout
usage: paconn [-h] [--verbose] [--debug] [--output {json,jsonc,table,tsv}] [--query JMESPATH]
{login,download,create,update,validate} ...
paconn: error: argument _command: invalid choice: 'logout' (choose from 'login', 'download', 'create', 'update', 'validate')

Download operation always prompts to select a connector when the connector id is provided as a parameter

Download operation always prompts to select a connector when the connector id is provided as a parameter

Persist login with token or similar

I'm asked to login very frequently, which disrupts the development flow of the custom connector. Is it possible to specify something like an OAuth token so that I am persistently logged in?

This would also enable CI/CD of connectors.

Swagger Validator and paconn tool doesn't check for 'content_type' syntax

Describe the bug
Swagger Validator doesn't check for 'content_type' syntax in the swagger

To Reproduce
Below Swagger passed paconn tool and Swagger Validator
{
"in": "body",
"name": "body",
"required": true,
"schema": {
"default": {
"conten_type": "sdsd",
"encoding": "cp1251"
},
"properties": {
"conten_type": {
"description": "conten_type",
"title": "Content type",
"type": "string"
},
"encoding": {
"description": "encoding",
"enum": [
"cp1251",
"cp866",
"utf-8"
],
"title": "Encoding",
"type": "string"
}
},
"required": [
"conten_type",
"encoding"
],
"type": "object"
}
}

Expected behavior
The paconn and Swagger Validator should validate the content_type and its value. Please close the bug if this is a design of the tools.