Copy link to clipboard
Copied
Hello,
I'm managing an enterprise implementation of Adobe Sign for my University, and getting a 403 error when attempting to set up the e-signature integration with Jaggaer iBuy. Are there any required permissions settings we'd need to have in place for our service account or group within Adobe Sign? Especially interested to hear from anyone who has implemented this successfully as Jaggaer documentation is scarce to non-existent.
Thanks in advance,
Scott
Thank you for reaching out, and sorry about the trouble caused.
We have checked that you are using the Adobe Sign Enterprise plan. If you have an integration-related question, the experts can best answer it. Please contact our Adobe Sign Enterprise support team for the correct information. You may contact them using the steps in the following help document: https://adobe.ly/4nhBCrs.
Refer to the following help document for more information on Acrobat Sign Integration: https://adobe.ly/47mEtta
...Thank you. Changing the service account permission level got the integration working.
Best,
Scott
Copy link to clipboard
Copied
@dynamic_static most 403 errors for enterprise integrations point to a permissions or authentication mismatch rather than Jaggaer itself, so confirm these common items on the Adobe Sign side: the service account must have API access enabled and a role that permits creating and sending agreements (preferably an account admin or an API-enabled user), the integration key or OAuth client you’re using must be active and granted the correct scopes for Agreements and Webhooks, the integration key must be associated with the same Adobe Sign account that Jaggaer is attempting to call, any IP allowlist or firewall rules for your Adobe Sign account must include Jaggaer’s outbound IPs, the callback/webhook URL configured in Jaggaer must exactly match what’s registered in Adobe Sign (including scheme and trailing slash), and if you’re using a service account in a grouped or delegated setup check that group-level permissions don’t block API calls; if all of the above look correct, collect the failing request details (timestamp, integration key/client id, request endpoint, and full error body) and escalate to Adobe Sign support so they can trace the 403 and confirm whether it’s an account-level policy, an invalid key, or an allowlist/firewall issue.
Copy link to clipboard
Copied
Thank you for reaching out, and sorry about the trouble caused.
We have checked that you are using the Adobe Sign Enterprise plan. If you have an integration-related question, the experts can best answer it. Please contact our Adobe Sign Enterprise support team for the correct information. You may contact them using the steps in the following help document: https://adobe.ly/4nhBCrs.
Refer to the following help document for more information on Acrobat Sign Integration: https://adobe.ly/47mEtta.
Thanks,
Meenakshi
Copy link to clipboard
Copied
Thank you. Changing the service account permission level got the integration working.
Best,
Scott
Find more inspiration, events, and resources on the new Adobe Community
Explore Now