adobe / acrobat-sign Goto Github PK

Expected Behaviour
Support for OAuth2 client_credential grant type

As outlined in this blog post adobe is moving it OAuth support to Client Credential grant type.
Current esign api has deprecated the Integration key but not provided a suitable replacement.

https://blog.developer.adobe.com/important-update-for-developers-using-adobe-apis-bf25110d3b4

Actual Behaviour

No support for Client Credential grant type.
https://corporate.na1.adobesign.com/public/static/oauthDoc.jsp#accessTokenRequest

PARAMETER | VALUE | REQUIRED? | DESCRIPTION
grant_type | authorization_code | yes | Value must always be "authorization_code"

Hi,

The following API is dangerous and it would be good to document its intended usage
method: AgreementsApi::createAgreementView
parameter: agreementViewInfo

agreementViewInfo use CommonViewConfiguration, and CommonViewConfiguration has option: autoLoginUser

If we set autoLoginUser to true, the createAgreementView will return a url to automatically log in the user in as the token owner. The user will then see all the documents as the token owner. In OAuth2 scenario, usually, the Admin will set up the OAuth handshake, and the Signers/Viewers won't necessarily have an account with Adobe.

Please clarify:

1. what's the intended business scenario of using this autoLoginUser in API
2. what's the api to use to get a readonly view of the signing document, eg. for people in the cc list. We shouldn't need to ask the user to login to view the signing document

Thanks

Expected Behaviour

Directly specify the signing location of each signatory when creating an agreement（创建协议时直接指定每个签署者的签署位置）

Actual Behaviour

java sdk missing parameter

Reproduce Scenario (including but not limited to)

Steps to Reproduce

Platform and Version

Sample Code that illustrates the problem

Logs taken while reproducing problem

There are numerous differences and missing methods between the JAVA SDK and the API described here https://secure.na1.adobesign.com/public/docs/restapi/v6