Skip to main content

Hello,

 

Has anyone experienced this issue? I have followed Acumatica instructions to configure the eSign(https://github.com/Acumatica/Acumatica-eSign) but I’m getting the message below:

 

Unable to authorize access because the client configuration is invalid: invalid_request

 

 

Maybe the issue is related to the Redirect URI ? I don’t think that Esign.aspx is correct. 

 

From your end is it working? 

 

Thanks

Hi @jeffersonmacedo 

Please review the following article and confirm if you followed all the steps defined here,

https://github.com/Acumatica/Acumatica-eSign

Double check the Client ID and Redirect the URL once.

Thanks


Hi @manikantad18 , thanks for your reply.

 

Yes I did checked the steps from Acumatica’s github (I also mentioned in my question), I also have questioned about the Redirect URL… Not sure if it’s correct.

 

Is this feature working for your sites?


Hi @jeffersonmacedo  I have not tested this feature 

May be the issue is related to adobe

https://github.com/Acumatica/Acumatica-eSign/issues/4


In Germany I had a similar error message.
To fix it I used the API-URL https://partnerintegration.eu2.adobesign.com


In Germany I had a similar error message.
To fix it I used the API-URL https://partnerintegration.eu2.adobesign.com

Have you pointed the Redirect URL to /Pages/ES/ESign.aspx? 

I tried changing the API URL to partnerintegration as you mentioned but it bounces me to secure.au1


Yes, my redict URL is

https://instancename.app/Pages/ES/ESign.aspx


What you could also check;
With the Client Secret the first character was not carried along when copying! This also results in an error.


@jeffersonmacedo did you make any changes to the github code? Please try the customization for the Acumatica version from this page: 

Adobe went through a change with their OAuth using v2 which we addressed on the updated packages. This has been one of the more common issues I noticed users running into when implementing. So I would start here first.

 

I am also assuming you checked the “Enabled Scopes” and they are accurate? 

 

Adobe generates different URL based on your location and the closest servers. So while the URL you have the http://secure.au1.adobesign.com should be the URL for you, one more thing you can try is under ESign Account Info in Acumatica → under API URL try using https://partnerintegration.au1.adobesign.com/.


@jeffersonmacedo I just deployed it on an instance and it worked. It seems like your redirect URL was correct. However, one thing I noticed while setting up was that if you copy paste the Client ID and Secret straight from the Adobe platform, it sometimes artificially adds spaces at the end of those fields. When you copy/paste, please ensure these spaces are removed. Let me know if that works. 


Hi @Omar Ghazi ,

 

Thanks for checking this. It is no longer an issue for me, I could make it connect after changing the redirect URI to https://(Site name)/Main?ScreenId=MBES3010 this screen name is a customization that my dev team has adapted. (That’s the reason I asked about the ESign.aspx)

 

 

However, I did a few attempts on a fresh Acumatica instance with the original project from the link you shared and it didn’t work... I tried with the same Adobe account and just pointed the Redirect URI, pasted the Client ID and Secret making sure it did not have any space but the same message was displayed.

Have you tested it using an account from au1.adobesign.com? 

 

 

 


@jeffersonmacedo I am glad you got it sorted out. I have not specifically tested au1.adobesign.com but working with a few users who got different API URL assigned by Adobe when attempting to create the Client ID/Secret, I was able to test a few different URL’s which worked successfully.  

Unfortunately, the error message on the Adobe login/authentication page isn’t very descriptive so we had to perform some trial and error. The majority of the issues we found during this experience on configuration of eSign, whether doing it ourselves or helping partners and customers, has been on either the Client ID/Secret copy/pasting with spaces, or the whitelisting address (redirect URI) being incorrect (which was typically the ESign.aspx on a live Acumatica site). 


Reply