We are using the Rest V2 API to create an envelope with a document in it. We then redirect the user to the page for them to complete the document (drag tag etc). using the demo server and our developer login we get a message saying the user has been logged out due to inactivity. On the production site with a production account it works OK. We can log into the demo site without issue with our account.
There was a bug in the new version (which goes on demo.docusign.net first), that bug should be addressed by now. The great news is that no production servers were affected and by the time the new version will make it to production the bug will be fixed. I believe demo servers will get the fix tomorrow.
Thanks for choosing DocuSign API!
Related
DocuSign have recently released Click Wraps at their Momentum. I would like to take advantage of this new feature and was exploring this a little.
Once, I was able to add a few click wrap templates using my DocuSign sandbox account but at times, I do not see them when I click on "Manage" button once I login to my DocuSign demo account.
Please advise,
Thanks,
Minal
Hmmm. I suggest checking that you're logged into your DocuSign demo account (Developer Sandbox) as the administrator. Login via https://demo.docusign.net
Sometimes people login to a trial version of the DocuSign production systems by mistake (https://www.docusign.net). While Click agreements are provided in all demo accounts, they are only provided for some customer pricing plans on the production systems.
If the problem continues, you can create a demo account. Or contact DocuSign customer service.
We had a similar issue here and as a workaround after we logged into our demo account we were able to enter the url for the clickwraps directly to navigate to the clickwraps page.
https://appdemo.docusign.com/documents?view=active&type=clickwraps
I'm using google apps for mail service. I have generated and submitted DKIM records for .co and .in domains successfully. But I'm not able to generate DKIM record for .net domain (say yourdomain.net). It shows an error we are unable to process your request at this time. Please try again later. (Error #1000). I have tried this for 2 .net domains. Both provide the same error. I have tried using in different browser and different machine, and the results are the same.
I am not sure if the issue is with the .net domain or if this is just a coincidence.
Had the same issue today (setup of DKIM on a new GSuite domain) and chatted with Google Support about it.
They pointed me to the following quote on the DKIM setup process.
Important: After you create your G Suite account and turn on Gmail, you must wait 24–72 hours before you can generate a DKIM domain key.
So you'll need to wait 24 - 72 hours after setup of the GSuite account before you can set up DKIM.
I also asked the support person whether I could get access to submit this as a product request (that the DKIM setup is prevented before this time) and he gave me access to the G Suite Feature Ideas (customers only) Cloud Connect Community. I've posted this as a feature suggestion there - upvote if you think this is needed! (needs login):
https://www.cloudconnectcommunity.com/ccc/ls/community/g-suite-chrome-feature-ideas/post/5075513382141952
Preview Screenshot:
I had a "Google Apps for Work" account and wanted to setup DKIM for Google Apps email and another provider and I couldn't do it. I contacted Google Apps support and they said it was a bug with no immediate plans to fix it.
I got the same useless error code you did. I'm disappointed in Google about this. They just leave the broken submit form up, leaving it to the user to contact support to find out it's broken with no plans to fix it.
I'm going to cancel my paying google apps account.
I experienced the same error message when I tried to set up DKIM immediately after signing up for GSuite. It worked when I re-tried about two days later.
I am trying to add a docusign connect listener but when I click on switch to classic application, it takes me back to new application landing page. I have a professional account. Please tell me if I am doing anything wrong?
You need to use your free developer sandbox account to test DocuSign Connect, not your paid production account. If you do an API Integration that uses Connect and you want to enable in production environment then you need go through DocuSign's API Certification Process. Login to your dev account and the switch back to Classic will work.
To create a free dev sandbox check out the home page:
https://www.docusign.com/developer-center
And see the Go Live section for information regarding API Certification: https://www.docusign.com/developer-center/go-live/overview
I have an asp.net mvc 5 site currently hosted on windows azure.
Occasionally (normally after I have rolled out or deployed to azure) the authentication seems to bug out.
I try to log in with my google account and I get weird redirect loops where I hit login, and it takes me straight back to the login page. This is normally fixed by restarting the site on windows azure again.
Every now and again though, it will redirect back from google and ask me to enter my username to complete the registration process. It does this on my google account that has already been registered. It is registering the same google account twice or sometimes even three times.
Its happened to myself and my users and I only hear about it when someone contacts me and tells me they've lost all their stuff linked to their profile on my site.
Has anyone experienced anything like this? I'm using the bog standard login / auth controller with an mvc5 project.
EDIT ::
my url is www.dev-score.com, but it also responds to just simply dev-score.com
could it be the fact that some people register on www.dev-score.com and then try to log in with simply dev-score.com or something like that?
sorry everyone, i feel kind of stupid now.
the reason this is happening is because of the different domains, not different url's.
by default azure also has a ".azurewebsites.net" domain that a few of my users were using while my .com domain was propagating.
when i switched to my .com domain, and disabled my .azurewebsites.net domain they all had to re-register, as google (rightfully) thinks that this is a new website.
these are the people that were experiencing that bug and i had to manually move their stuff over to their new accounts. every now and again a user from that period comes back to the site and logs in and has to go through this process again, so it seemed like an intermittent bug but its not, its only a bug to those few users that registered during that small window and haven't been back to the site since.
I have developed an integration using docusign SOAP API. We had the integration certified. It works great using the demo API URLs and my dev account. When I update the API URLs to production and use my live production account I get the return status of "One or both of Username and Password are invalid" when I call CreateEnvelope(). I have verified the user name and password are correct. I use them to log into the production account. I am setting the username in the code like [APIKEY]APIUSERNAME.
Does a DocuSign account need to be authorized to use an integration? How do I know my integrators key was moved over to production after certification? Any ideas when this works in dev but not in production.
Just wanted to follow up and post the answer to this issue. After working with Partner support I was able to get things working.
The issue was related to using the wrong base url when I created my api proxy. I was just passing in the docusign production url, when I actually needed to get this in the configuration for each user that uses the integration. When I get the base url in the config part of the app it return the actual server which the users account resided on (which includes the na1 or na2 etc server name in the url). After adding this to the config and using this new base url in my calls the app works as it should.
Yes I believe DocuSign production accounts need to be authorized to use the API. If you are positive that you are passing the correct username and password in your code then it's quite possible that this is an account issue.
For resolution I would suggest the following. For questions regarding your integration key and if it was indeed promoted to production following your successful certification you should contact
apicertifications#docusign.com
And if you have an account manager you might want to try reaching out to them as well, which might get your questions answered sooner.