- Momentum_InstoreAsked on February 14, 2018 at 12:07 PM
We are constantly struggling with the AdobeSign widget. It works OK for a couple of weeks but then stops working. We now cant re-authenticate the widget. We have tried signing out of both JotForm and AdobeSign and clearing the browser cache, before resigning in. When we try to authenticate the widget it brings up the AdobeSign login window. We enter the login name and then as soon as we click on the password box it trys to sign in before we have chance to enter a password (no password is cached). It does sign us in to Adobe sign (even without us entering the password) but JotForm still says it needs to be authenticated. AdobeSign shows a valid access token.
All in all the integration seems incredibly flakey and we are struggling to get any support.
- JotForm SupportRichie_PAnswered on February 14, 2018 at 01:26 PM
I made a form with the Adobe Sign widget and I can't seem to replicate the issue.
Can you try to login to your Adobe Sign account first, then authenticate the widget?
When you input your email address, it will load for a few seconds and you would be redirected to adobe sign.
Let us know how it goes.
If the issue still remains, may we know the Form URL you're using that has Adobe Sign widget?
- Momentum_InstoreAnswered on February 15, 2018 at 04:36 AM
Yep we've done that and get the screen above. But JotForm still says its not authenticated and people we are sending the form to are unable to send it. The integration just seems incredibly flakey.
- JotForm SupportVictoria_KAnswered on February 15, 2018 at 07:26 AM
It seems that we already have an opened issue with users being unable to authenticate to Adobe Sign.
I have checked it's status and the priority is set to "IMPORTANT", that means that our developers are fixing it right now.
Meanwhile, please try using the Private Mode (Incognito) of your browser.
The authentication should ask for login credentials again. You might want to check Activate Signer Flow in the widget for it to work. You can check the thread I have shared below for more information and updates.
We do apologize for the inconvenience caused.