When transfering integration between two syndesis instances: Unable to decrypt key:accessToken

This is a…

[ ] Feature request
[ ] Regression (a behavior that used to work and stopped working in a new release)
[ x ] Bug report  
[ ] Documentation issue or request

The problem

I’m unable to transfer integration from one syndesis instance to another. The connections (twitter and salesforce in my case) used by the integration use the “basic connection configuration” I don’t use the “OAuth Application Management”. After I updated both connections (Orange triangle “Configuration required”), I tried to publish the integration. The server log provides following error:

2018-05-10 07:52:42.744 ERROR [-,,,] 1 --- [tion Controller] i.s.s.c.integration.online.BaseHandler   : Integration [twitter-salesforce]: [ERROR] Activation failure

java.lang.IllegalArgumentException: Unable to decrypt key:accessToken
	at io.syndesis.integration.project.generator.ProjectGeneratorHelper.mandatoryDecrypt(ProjectGeneratorHelper.java:133) ~[integration-project-generator-1.3.5.fuse-000002-redhat-1.jar!/:1.3.5.fuse-000002-redhat-1]
	at io.syndesis.integration.project.generator.ProjectGenerator.addDecryptedKeyProperty(ProjectGenerator.java:223) ~[integration-project-generator-1.3.5.fuse-000002-redhat-1.jar!/:1.3.5.fuse-000002-redhat-1]
	at io.syndesis.integration.project.generator.ProjectGenerator.generateApplicationProperties(ProjectGenerator.java:151) ~[integration-project-generator-1.3.5.fuse-000002-redhat-1.jar!/:1.3.5.fuse-000002-redhat-1]
	at io.syndesis.server.controller.integration.online.PublishHandler.createDeploymentData(PublishHandler.java:131) ~[server-controller-1.3.5.fuse-000002-redhat-1.jar!/:1.3.5.fuse-000002-redhat-1]
	at io.syndesis.server.controller.integration.online.PublishHandler.execute(PublishHandler.java:100) ~[server-controller-1.3.5.fuse-000002-redhat-1.jar!/:1.3.5.fuse-000002-redhat-1]
	at io.syndesis.server.controller.StateChangeHandler.execute(StateChangeHandler.java:33) [server-controller-1.3.5.fuse-000002-redhat-1.jar!/:1.3.5.fuse-000002-redhat-1]
	at io.syndesis.server.controller.integration.IntegrationController.lambda$callStateChangeHandler$11(IntegrationController.java:196) [server-controller-1.3.5.fuse-000002-redhat-1.jar!/:1.3.5.fuse-000002-redhat-1]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) ~[na:1.8.0_171]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) ~[na:1.8.0_171]
	at java.lang.Thread.run(Thread.java:748) ~[na:1.8.0_171]

2018-05-10 07:52:42.744 INFO [-,,,] 1 --- [tion Controller] i.s.s.c.i.IntegrationController : Integration i-LC7vFY2P96ad_t7Pzytz : Setting status to Pending (Unable to decrypt key:accessToken)

Expected behavior

The integration should get published after user updates the connections.

Request and Response Data

Attached the exported integration (created on CR1): twitter_salesforce-export.zip

Server log: server_log.txt

Tasks involved / Steps to Reproduce

1. Start two syndesis instances (or you can simply use the attached integration)
2. Create integration TW->SF on one instance, export it
3. Import to second instance, update the connections
4. Publish integration
5. observe errors in server log, the integration will stay in “Publishing” state indefinitely

[lburgazzoli]

@tplevko yes it is a workaround

there is a general issue about the relation of an integration and external objects such as connections that we need to discuss.

[tplevko]

@lburgazzoli for now, as there is this workarround, I’ll let documentation team know, so they could cover it in our docs. I think however it would be good, if this got solved in a more intuitive way in the future.