Merge branch 'microsoft:dev' into c2_branch

certified-connectors/Dokobit Universal API/apiProperties.json

@@ -0,0 +1,23 @@
+{
+  "properties": {
+    "connectionParameters": {
+      "api_key": {
+        "type": "securestring",
+        "uiDefinition": {
+          "displayName": "API Key",
+          "description": "The API Key for this api",
+          "tooltip": "Provide your API Key",
+          "constraints": {
+            "tabIndex": 2,
+            "clearText": false,
+            "required": "true"
+          }
+        }
+      }
+    },
+    "iconBrandColor": "#2A0062",
+    "capabilities": [],
+    "publisher": "Dokobit",
+    "stackOwner": "Dokobit"
+  }
+}

certified-connectors/Dokobit Universal API/readme.md

@@ -0,0 +1,84 @@
+# Dokobit Universal API
+Dokobit Universal API is a versatile tool that enables signing documents internally, within your system, and collecting signatures from 3rd parties, outside your system, across Europe. Document signing occurs in an accountless Dokobit signing (where invited participants can sign documents without registering on the Dokobit portal) interface with your organisation’s branding.
+
+## Publisher: Dokobit
+
+## Prerequisites
+In order to use Dokobit Universal API contact us at sales@dokobit.com to obtain the API access token.
+
+## Supported Operations
+
+### Create External Signing
+External signing initiates asynchronous signing request from your system. In this case user receives an email for signing and you will get a callback once he signs the document.
+
+### Check External Signing Status
+Returns document's information with signing status.
+
+### Download Document External
+Downloads the signed document.
+
+### Send Reminder
+Allows to send a reminder e-mail for participant, only if person has not signed document yet. Only works with external signing flow.
+
+### Add External Signer
+Indicated participants will gain access to the document with the selected role.
+
+### Delete External Signer
+Access to the document will be revoked for the indicated participant.
+
+### Delete External Signing
+The document will be removed from the owner's account. It will remain accessible to other participants.
+
+### Update External Signing
+Allows to update attributes of an existing document signing.
+
+### Create Internal Signing
+Internal signing initiates signing request from your system. In this case signing URL is generated where participant should be redirected.
+
+### Check Internal Signing Status
+Returns document's information with signing status.
+
+### Download Document Internal
+Downloads the signed document.
+
+### Add Internal Signer
+Indicated participants will gain access to the document with the selected role.
+
+### Delete Internal Signer
+Access to the document will be revoked for the indicated participant.
+
+### Delete Internal Signing
+The document will be removed from the owner's account. It will remain accessible to other participants.
+
+### Update Internal Signing
+Allows to update attributes of an existing document signing.
+
+### Seal signing
+Document will be sealed with your organizations' electronic seal. Please contact our support at developers@dokobit.com to get a qualified certificate for e-sealing.
+
+### e-Delivery
+Document e-Delivery is used for securely sharing documents via Dokobit Universal API.
+
+### Validation
+Dokobit is an eIDAS-certified service provider for qualified e-signature and e-seal validations. Use this action to upload a signed file for validation. Supported file types: `asice`, `asics`, `sce`, `bdoc`, `edoc`, `pdf`, `p7s`, `xml`.
+
+### Validation - Detailed PDF Report
+Download detailed validation report in PDF.
+
+### Validation - XML Diagnostic Data
+Download diagnostic data in XML.
+
+### Validation - PDF Report
+Download validation report in PDF.
+
+### Validation - XML Report
+Download validation report in XML.
+
+## Obtaining Credentials
+[Contact](mailto:sales@dokobit.com) our Sales to get the API access token.
+
+## Known Issues and Limitations
+The current implementation supports signature gathering on PDF files and supported by ASiCe, ADoc, BDoc or EDoc containers.
+
+## Deployment Instructions
+Please use [these instructions](https://docs.microsoft.com/en-us/connectors/custom-connectors/paconn-cli) to deploy this connector as a custom connector within Microsoft Power Automate and Power Apps.

certified-connectors/Microsoft Bookings/Readme.md

@@ -7,9 +7,8 @@ This is a Microsoft Bookings connector. Microsoft Bookings is a scheduling tool
 
 You will need the following to proceed:
 
-- A Microsoft Power Apps or Microsoft Power Automate plan with custom connector feature
-- An Azure subscription
-- [Microsoft Power Platform Connectors CLI](https://github.com/microsoft/PowerPlatformConnectors/tree/master/tools/paconn-cli)
+- A Microsoft Power Apps or Microsoft Power Automate plan
+- One of the licesnses that support Microsoft Bookings
 
 ## Supported Operations
 
@@ -20,37 +19,4 @@ Triggers for appointment Create action
 Triggers for appointment Update action 
 
 ### Appointment Cancelled
-Triggers for appointment Cancel action 
-
-## Obtaining Credentials
-
-### Registering an Azure Active Directory application
-
-Since the connector retrieve information about users and user-relationships stored in Azure Active Directory (AD), we need to register a [client application](https://docs.microsoft.com/en-us/azure/active-directory/develop/developer-glossary#client-application) in Azure AD to create and test the connector. The user of Power Apps or Power Automate will authorize this application to access the Microsoft Graph API on user's behalf. [Here](https://docs.microsoft.com/en-us/azure/active-directory/develop/authentication-scenarios) is a great resource to understand the basics of authentication.
-
-Please follow the steps as below:
-
-1. Register a new application by following the steps [here](https://docs.microsoft.com/en-us/azure/active-directory/develop/quickstart-register-app). When configuring the application, use following selections:
-
-   - **Supported account types** Select an option based on whether you would restrict users to your application's Azure AD tenant or if you would allow users from other tenants.
-   - **Redirect URI** Select 'Web' and enter 'https://global.consent.azure-apim.net/redirect'.
-
-2. After the app is registered, open 'API permissions' page from application's sidebar and click 'Add a permission'. Now select 'Micrsoft Graph' > 'Delegated permissions' and add all permissions as defined in [apiProperties.json](apiProperties.json) i.e. `Bookings.Readwrite.All, Bookings.Read.All`.
-
-3. Open 'Certificates and secrets' page and click 'New client secret' > 'Add'. This will create a new row with secret. Note down the secret value somewhere. It is displayed only once.
-
-4. Open Overview page and note down the value of 'Application (client) ID'.
-
-## Known Issues and Limitations
-We do not have any known issues so far
-
-## Deployment Instructions
-
-1. Make sure that you have [Microsoft Power Platform Connectors CLI](https://github.com/microsoft/PowerPlatformConnectors/tree/master/tools/paconn-cli) installed.
-2. Clone this GitHub repo. Open the command shell and change to this directory.
-3. Open file [apiProperties.json](apiProperties.json). Use the client ID you noted down above as the value of `clientId` property.
-4. Run the following commands with `<clientSecret>` replaced with the actual client secret and follow the prompts:
-
-```
-paconn create --api-def apiDefinition.swagger.json --api-prop apiProperties.json --secret <clientSecret>
-```
+Triggers for appointment Cancel action