Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Partner Centre Certification Process #3567

Open
Encodian opened this issue Jul 4, 2024 · 1 comment
Open

Partner Centre Certification Process #3567

Encodian opened this issue Jul 4, 2024 · 1 comment

Comments

@Encodian
Copy link
Contributor

Encodian commented Jul 4, 2024

Hello Team

We are following the new process however there are a few issues we cannot circumvent:

  1. We cannot add our connector to a Power Automate solution to verify using the solution checker due to the following error: The request failed with error: '{"error":{"code":"0x80044331","message":"A validation error occurred. The length of the 'openapidefinition' attribute of the 'connector' entity exceeded the maximum allowed length of '500000'."}}'.
  2. We cannot use paconn either as it is generating the following error upon validation:
    HTTPSConnectionPool(host='api.powerapps.com', port=443): Max retries exceeded with url: /providers/Microsoft.PowerApps/objectIds/71b6b311-8a5e-4e52-88c6-07e0e1301290/validateApiSwagger?api-version=2016-11-01&enableConnectorCertificationRules=true (Caused by SSLError(SSLEOFError(8, 'EOF occurred in violation of protocol (_ssl.c:2384)')))
  3. We cannot use paconn download, as after selecting the environment the following error occurs:
    {
    "error": {
    "code": "InvalidAuthenticationToken",
    "message": "The received access token has been obtained from wrong audience or resource."
    }
    }
    401 Client Error: Unauthorized for url: https://api.powerapps.com/providers/Microsoft.PowerApps/apis?api-version=2016-11-01&%24filter=environment****redacted
    ****

Can you advise please?

@pablodiazgutierrez
Copy link

Did you figure this out? We're trying to update our connector and we run into your 3rd point as well. I see that paconn 0.0.21 is supposed to have resolved this, as per other tickets, but it's still throwing that error on my console...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants