Penneo Certified Connectors

[yeu1]

Penneo Certified Connectors

Summary

This PR adds four new certified connectors for Penneo, a digital signing platform. The connectors enable OAuth authentication and case file creation workflows in both production and sandbox environments.

Connectors Added

Penneo Pluto Auth

OAuth connector that exchanges API keys for JWT access tokens using Penneo's custom OAuth flow with WSSE authentication.

Penneo Pluto Auth Sandbox

Sandbox version of the OAuth connector for testing and development.

Penneo Simple CaseFile Creation

Creates case files with documents and signers, and checks asynchronous job status. Requires JWT token from Pluto Auth connector.

Penneo Simple CaseFile Creation Sandbox

Sandbox version of the case file creation connector.

Key Features

• Custom OAuth flow with API key authentication
• Asynchronous case file creation with job status tracking
• Base64 document encoding support
• Production and sandbox environment support

Files Added

• certified-connectors/Penneo Pluto Auth/
• certified-connectors/Penneo Pluto Auth Sandbox/
• certified-connectors/Penneo Simple CaseFile Creation/
• certified-connectors/Penneo Simple CaseFile Creation Sandbox/

---

When submitting a connector, please make sure that you follow the requirements below, otherwise your PR might be rejected. We want to make you have a well-built connector, a smooth certification experience, and your users are happy :)

If this is your first time submitting to GitHub and you need some help, please sign up for this session.

• I attest that the connector doesn't exist on the Power Platform today. I've verified by checking the pull requests in GitHub and by searching for the connector on the platform or in the documentation.
• I attest that the connector works and I verified by deploying and testing all the operations.
• I attest that I have added detailed descriptions for all operations and parameters in the swagger file.
• I attest that I have added response schemas to my actions, unless the response schema is dynamic.
• I validated the swagger file, apiDefinition.swagger.json, by running paconn validate command.
• If this is a certified connector, I confirm that apiProperties.json has a valid brand color and doesn't use an invalid brand color, #007ee5 or #ffffff. If this is an independent publisher connector, I confirm that I am not submitting a connector icon.

If you are an Independent Publisher, you must also attest to the following to ensure a smooth publishing process:

• I have named this PR after the pattern of "Connector Name (Independent Publisher)" ex: HubSpot Marketing (Independent Publisher)
• Within this PR markdown file, I have pasted screenshots that show: 3 unique operations (actions/triggers) working within a Flow. This can be in one flow or part of multiple flows. For each one of those flows, I have pasted in screenshots of the Flow succeeding.
• Within this PR markdown file, I have pasted in a screenshot from the Test operations section within the Custom Connector UI.
• If the connector uses OAuth, I have provided detailed steps on how to create an app in the readme.md.

[yeu1]

@microsoft-github-policy-service agree company="Penneo A/S"