q5nrb (q5nrb) asked a question.
Hi,
The current DocuSign connector seems hardcoded towards account.docusign.com. Any chance there will be an option to connect with account-d.docusign.com soon-ish?
Cheers,
Mads
Hello @q5nrb (q5nrb),
My recommendation on this case is to open a request on Okta Ideas for this feature on specific, please check the following link with information: https://support.okta.com/help/s/article/Okta-Ideas-Step-by-Step-Guide?language=en_US
Regards,
Natalia
Okta Inc.
In addition to what Natalia provided. It appears Docusign supports Authorization Code (https://developers.docusign.com/platform/auth/authcode/authcode-get-token/)
This is the only Oauth grant type at present natively supported by Workflows. This means you should be able to leverage the API connector card with an Oauth connection to the "Sandbox/Dev" environment. This would effectively work like the "Custom API Action" available on the specific App card but it would leverage the full URL instead of a Relative URL to the endpoint.
Yes, thanks @TimL.58332 (Workflows) - it works!
I created a new app in DocuSign with this redirect URI:
https://oauth.workflows.oktapreview.com/oauth/httpfunctions/cb
Then configured the API connector:
And now the workflow works - sets a user's Login Policy to IdP only:
Note the base url is api-d.docusign.net
If anyone comes across this thread, note that my scope is missing "extended".
Reference: https://developers.docusign.com/platform/auth/reference/scopes/
Alright, I just want to finish off with while this works, it is not optimal. For a custom cal like the above, sure. However, I cannot build flows with the DocuSign app action cards, meaning I can't build and validate flows in preview/dev before importing to production.
We use cookies to provide the best website experience and to help understand marketing efforts. We may also share data with ad partners to reach potential customers across the web. To learn more, visit our Privacy Policy. Click here for Your Privacy Choices. You may also opt out of this sharing by signaling your preference via GPC, applicable only to the browser signaling the opt-out.
More information
These cookies are necessary for the website to function and cannot be switched off in our systems. They are usually only set in response to actions made by you which amount to a request for services, such as setting your privacy preferences, logging in or filling in forms. You can set your browser to block or alert you about these cookies, but some parts of the site will not then work. These cookies do not store any personally identifiable information.
These cookies enable the website to provide enhanced functionality and personalisation. They may be set by us or by third party providers whose services we have added to our pages. If you do not allow these cookies then some or all of these services may not function properly.
These cookies allow us to count visits and traffic sources so we can measure and improve the performance of our site. They help us to know which pages are the most and least popular and see how visitors move around the site. All information these cookies collect is aggregated and therefore anonymous. If you do not allow these cookies we will not know when you have visited our site, and will not be able to monitor its performance.
These cookies may be set through our site by our advertising partners. They may be used by those companies to build a profile of your interests and show you relevant adverts on other sites. They do not store directly personal information, but are based on uniquely identifying your browser and internet device. If you do not allow these cookies, you will experience less targeted advertising.
Select All
We use cookies to provide the best website experience and to help understand marketing efforts. We may also share data with ad partners to reach potential customers across the web. To learn more, visit our Privacy Policy. Click here for Your Privacy Choices. You may also opt out of this sharing by signaling your preference via GPC, applicable only to the browser signaling the opt-out.
More information
These cookies are necessary for the website to function and cannot be switched off in our systems. They are usually only set in response to actions made by you which amount to a request for services, such as setting your privacy preferences, logging in or filling in forms. You can set your browser to block or alert you about these cookies, but some parts of the site will not then work. These cookies do not store any personally identifiable information.
These cookies enable the website to provide enhanced functionality and personalisation. They may be set by us or by third party providers whose services we have added to our pages. If you do not allow these cookies then some or all of these services may not function properly.
These cookies allow us to count visits and traffic sources so we can measure and improve the performance of our site. They help us to know which pages are the most and least popular and see how visitors move around the site. All information these cookies collect is aggregated and therefore anonymous. If you do not allow these cookies we will not know when you have visited our site, and will not be able to monitor its performance.
These cookies may be set through our site by our advertising partners. They may be used by those companies to build a profile of your interests and show you relevant adverts on other sites. They do not store directly personal information, but are based on uniquely identifying your browser and internet device. If you do not allow these cookies, you will experience less targeted advertising.
Select All
In addition to what Natalia provided. It appears Docusign supports Authorization Code (https://developers.docusign.com/platform/auth/authcode/authcode-get-token/)
This is the only Oauth grant type at present natively supported by Workflows. This means you should be able to leverage the API connector card with an Oauth connection to the "Sandbox/Dev" environment. This would effectively work like the "Custom API Action" available on the specific App card but it would leverage the full URL instead of a Relative URL to the endpoint.