Hi Team,
I am developing the custom outbound connector.
I added secrets in the connector secrets section. But its not picking as per expectation. I am getting below exception. Could you please help me on it ?
Exception:
io.camunda.connector.api.error.ConnectorInputException: Secret with name ‘ACCESS_KEY’ is not available
Hi @vinothkumar ,
Could you please share some more information about your setup? Is it SaaS? Or Self-managed? If the latter, then which connector runtime are you using? Do you use the default secret provider or a custom one? How do you add your secrets?
Hi @mark.farkas ,
Can you plz give a guide here.
still I am getting below errors when I try to access,
io.camunda.connector.api.error.ConnectorInputException: Secret with name ‘AWS_ACCESS_KEY’ is not available
at io.camunda.connector.runtime.core.secret.SecretHandler.lambda$new$0(SecretHandler.java:38)
at java.base/java.util.Optional.orElseThrow(Optional.java:403)
at io.camunda.connector.runtime.core.secret.SecretHandler.lambda$new$1(SecretHandler.java:35)
at io.camunda.connector.runtime.core.secret.SecretUtil.resolveSecretValue(SecretUtil.java:72)
at io.camunda.connector.runtime.core.secret.SecretUtil.lambda$replaceSecretsWithParentheses$0(SecretUtil.java:50)
at io.camunda.connector.runtime.core.ConnectorUtil.replaceTokens(ConnectorUtil.java:93)
at io.camunda.connector.runtime.core.secret.SecretUtil.replaceSecretsWithParentheses(SecretUtil.java:47)
at io.camunda.connector.runtime.core.secret.SecretUtil.replaceSecrets(SecretUtil.java:37)
at io.camunda.connector.runtime.core.secret.SecretHandler.replaceSecrets(SecretHandler.java:42)
at io.camunda.connector.runtime.core.outbound.JobHandlerContext.getJsonReplacedWithSecrets(JobHandlerContext.java:65)
at io.camunda.connector.runtime.core.outbound.JobHandlerContext.mapJson(JobHandlerContext.java:71)
at io.camunda.connector.runtime.core.outbound.JobHandlerContext.bindVariables(JobHandlerContext.java:58)
at io.cg.camunda.connector.MyConnectorFunction.execute(MyConnectorFunction.java:37)
at io.camunda.connector.runtime.core.outbound.ConnectorJobHandler.handle(ConnectorJobHandler.java:105)
at io.camunda.connector.runtime.outbound.jobhandling.SpringConnectorJobHandler.lambda$handle$0(SpringConnectorJobHandler.java:75)
at io.micrometer.core.instrument.AbstractTimer.record(AbstractTimer.java:247)
at io.camunda.zeebe.spring.client.actuator.MicrometerMetricsRecorder.executeWithTimer(MicrometerMetricsRecorder.java:52)
at io.camunda.connector.runtime.outbound.jobhandling.SpringConnectorJobHandler.handle(SpringConnectorJobHandler.java:66)
at io.camunda.zeebe.client.impl.worker.JobRunnableFactoryImpl.executeJob(JobRunnableFactoryImpl.java:45)
at io.camunda.zeebe.client.impl.worker.JobRunnableFactoryImpl.lambda$create$0(JobRunnableFactoryImpl.java:40)
at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:577)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:317)
at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642)
at java.base/java.lang.Thread.run(Thread.java:1589)
Hi Team,
Anyone else can help on this ?
Hi @mark.farkas ,
Any help
I have the same issue. The secrets are not accessible even using {{ syntax.
Its a self managed version running in my Mac.
The error is Secret with name ‘CUSTOMER_APP_SECRET’ is not available
Hi @tharansakthi - this topic is more than 1 year old; can you start a new topic for your issue? Please include what version of Camunda you’re running and how you have it deployed (Docker, Kubernetes/Helm, etc.), as well as the relevant configuration for the Connectors Runtime.
