We are doing some work around AEM Forms and Adobe Sign.
Our Adobe Sign accounts are hosted on either the EU1 or NA2 domain.
We have noticed that this does nto work in this case. It appears that only accounts hosted on NA1 work.
We have updated to replace instances of na1 with na2
- /libs/adobesign/components/adobesigncloudservice/adobesignpage/dialog/items/general/items/webaccesspoint
- /libs/adobesign/components/adobesigncloudservice/adobesignpage/dialog/items/general/items/refreshtokenuri
- /libs/adobesign/components/adobesigncloudservice/adobesignpage/dialog/items/general/items/oAuthUrl
- /libs/adobesign/components/adobesigncloudservice/adobesignpage/dialog/items/general/items/apiaccesspoint
- /libs/adobesign/components/adobesigncloudservice/adobesignpage/dialog/items/general/items/accesstokenuri
- /etc/cloudservices/echosign/jcr:content
This allows us to connect during cloud config, BUT we are still unable to submit a form for sign.
In the log we see a request being made to the NA1 server
25.10.2017 19:55:53.654 *DEBUG* [86.172.113.235 [1508961350736] POST /content/forms/af/sign/jcr:content/guideContainer.af.agreement.jsp HTTP/1.1] org.apache.http.impl.conn.PoolingHttpClientConnectionManager Connection request: [route: {s}->https://secure.na1.echosign.com:443][total kept alive: 0; route allocated: 0 of 2; total allocated: 0 of 20]
and a stack dump
We get a stack dump in the log at
Caused by: com.adobe.sign.utils.ApiException: Request must be made to correct API access point (e.g. use GET /base_uris).
at com.adobe.sign.utils.ApiClient.invokeAPI(ApiClient.java:562)
at com.adobe.sign.api.TransientDocumentsApi.createTransientDocument(TransientDocumentsApi.java:94)
at com.adobe.aem.adobesign.service.impl.AdobeSignServiceImpl.uploadTransientDocument(AdobeSignServiceImpl.java:470)
We are wondering if there is any code that has https://secure.na1.echosign.com hard coded rather via a config entry,
Has anyone else come across this?
Thanks
