CODEWITHSUNDEEP
oauth-2.0docusignapipower-automatepower-automate-custom-connector
Eric
Eric

Reputation: 1068

DocuSign Power Apps Custom Connector not working

I am setting up the DocuSign rest connector in power apps. I have other API's that working well this same way.

I want to get this setup to sweep completed files on a scheduled.

I started by going through this tutorial and tried the same setup. But when I try to test the connector I don't get prompted for credentials. We use SSO - so the window comes up and goes away without an error message.

https://www.docusign.com.au/blog/get-the-flow-sending-docusign-envelopes-microsoft-power-automate

I then tried to create a connection in in power automate Data/Connections and get an error message after entering my dev credentials. The clientid (integration key) and the secret match.

OAuth2 authorization flow failed for service 'Generic Oauth 2'. OAuth 2 sign in failed to exchange code for access token. Client ID and secret sent in form body.. Response status code=NotFound. Response body: { "statusCode": 404, "message": "Resource not found" } Client ID and secret sent in Basic authorization header.. Response status code=NotFound. Response body: { "statusCode": 404, "message": "Resource not found" }

The setup looks correct. It seems like a reference problem = like the production account and the developer account are not in sync or something. I have the same email address for both production and developer accounts and we use SSO - maybe its trying to reference production and not the developer account when its logging in? Just guessing.

I have a ticket with them, but they have note been able to help so far and they are on AEST time and I won't be able to get a response back from them for another couple of days :(

(I tried using the DocuSign Git repo API to create the connection as well - same problem)

Anyone have problems like this or know a solution? Anything else I can look at. This seems all straight forward -standard OAuth setup.

Using this setup like in the article for the demo (dev) account.

DEMO: IKey: Integration Key [captured earlier]

Secret Key: Secret Key [captured earlier]

Authorization URL (DEMO): https://account-d.docusign.com/oauth/auth

Token URL (DEMO): https://account-d.docusign.com/oauth/token

Refresh URL (DEMO): https://account-d.docusign.com/oauth/token

Scope: signature extended

Upvotes: 0

Views: 607

Answers (1)

Mohamed Ali
Mohamed Ali

Reputation: 29

This will connect to a single DocuSign user (like a "service account"). It will not prompt each user for their credentials. You will need 1 generic user setup within your DocuSign account, without SSO (you can setup an exception user in DocuSign admin. This is best practice when setting up SSO as a fallback in case SSO fails to login as well).

The envelope will be sent from that generic user, not the actual user. This is common practice with some "system level" integrations.

Also, are you connecting a DocuSign "demo" or production account? I ask because there's two connectors for power automate - "DocuSign" (for production) and "Docusign Demo" (for demo). I would recommend doing it all in demo first, as the "client id" (aka "integration key") needs to go through a go-live process to be promoted from demo to prod (see the link in the guide).

Upvotes: 1

Related Questions