I wrote a custom jira connector for camunda 8.8 (using camund sdk 8.8.14 on pom.xml). I can deploy my connector successfully within a k8s cluster. But when I run a process within webmodeler conntaing the connector, it is unfortunately not triggered. I don’t what is really the cause. I will provide you a snippet of manifest file for my connector and for my helm chart value for orchestration.
Connector
camunda:
client:
mode: self-managed
rest-address: https://host.com
grpc-address: http://camunda-zeebe-gateway:26500
prefer-rest-over-grpc: false
auth:
method: oidc
token-url: “https://host.com/auth/realms/camunda-platform/protocol/openid-connect/token”
client-id: ${CAMUNDA_CLIENT_AUTH_CLIENTID}
client-secret: ${CAMUNDA_CLIENT_AUTH_CLIENTSECRET}
audience: “orchestration-api”
Helm chart value
orchestration:
enabled: true
contextPath: “/orchestration”
ingress:
grpc:
enabled: true
className: nginx
host: “orchestration.host.com”
clusterSize: “1”
partitionCount: “1”
replicationFactor: “1”
security:
authentication:
method: oidc
oidc:
redirectUrl: “https://host.com/orchestration”
authUrl: “https://host.com/auth/realms/camunda-platform/protocol/openid-connect/auth”
tokenUrl: “https://host.com/auth/realms/camunda-platform/protocol/openid-connect/token”
jwksUrl: “https://host.com/auth/realms/camunda-platform/protocol/openid-connect/certs”
secret:
existingSecret: camunda-credentials
existingSecretKey: “identity-orchestration-client-token”
Notices:
- I replaced the original server url with host.com.
- The audience ‘orchestration-api‘ is correct. I checked it once within keycloak management portal.