Skip to Main Content
Nintex Ideas

đź‘‹ Use this site to provide feedback and ideas for all Nintex Products. See our post on Nintex Community "Welcome to Nintex Ideas" for more details on Nintex Ideas, how an idea is handled by our product teams and more!


If you have questions about Nintex Ideas, please contact ideas@nintex.com

If you require support, please visit Nintex Customer Central

If you have a sales inquiry, please contact sales@nintex.com

Status Completed
Created by Guest
Created on Jun 7, 2022

Docusign move to OAuth 2.0 will affect Nintex Drawloop DocGen customers using legacy ikey

DocuSign is introducing authentication based on OAuth 2.0 as per: https://developers.docusign.com/platform/auth/oauth2-requirements-migration/
DocGen customers may be using integration keys that are part of legacy setup.
This change will be enforced by October 2022 and will affect customers who fit the description.
If Nintex doesn't take the necessary action in time many customers will be affected. We need committment from Nintex to take action in time to avoid any disruption to customers' business processes.
Thank you!
  • Attach files
  • Guest
    Reply
    |
    Sep 8, 2022
    Thanks for this feedback. We are working towards a fix for the extended March '22 deadline and are currently defining the approach to minimize the impact on customers. We will share an update soon, once the approach has been agreed.