We've recently finished creating a K2 / Adobe Sign integration on our DEV environment.
This included creating an OAUTH Resource Type, Resource instance, Service Instance and Smart Objects. Customizations were made to a form to take advantage of the new Smart Object methods.
We are ready to move our project to our staging server. But I have some questions.
1. Do I need to create the OAUTH resources on the staging server PRIOR to the migration? Or,
2. Will the migration create the OAUTH resources on the staging server
3. Is there a document / link that details how to accomplish this?
Best answer by dadkindView original
You may want to checkout the package & Deployment considerations documentation in the link below.
Should you feel that this post is of use and or an accurate solution to the raised question, I kindly encourage you to mark it as such
using the 'Mark as Solution', 'Kudo' andor ‘Me Too’ options.
K2 will not accept any liability for any issues arising from actions taken in respect of the information provided by any forum member.
You might have to create the Oauth resources/types on the target environment before deploying any K2 packages. I did a similar test with UiPath integration where it requires setting up Oauth for the integration and I have to create it on both source/target vm.
The section labeled "Included and Excluded Artifacts" explains what I need to do.
@tomasv Which tutorials have you used in order to create K2 - Adobe Sign integration? Do you have any tips?
We started with this tutorial: https://www.k2.com/blog/using-electronic-signatures-in-k2-business-process-application (looks like he’s updated this since we used it).
The biggest stumbling block we encountered was with K2 documentation which had a bad callback link. Once we had the correct callback link, things started working.
This is the value of the redirect_url that we ended up using to get things to work (this was different in the docs): https://<servername>/identity/token/oauth/2
I hope this helps.