Authenticating for OPERATE failed due to java.lang.RuntimeException: Unable to authenticate due to missing Set-Cookie

Karthik_Bhat · September 4, 2024, 2:35pm

We are getting the above error when we are trying to enable authentication for the inbound with k8s config for connectors component.

We are using simple auth, also we have created the additional user which is connectors in open search manually as we can see that this particular user it is referencing in helm chart.

github.com

camunda/camunda-platform-helm/blob/ec031f27b95eaf56267976484cef3e7571bca0d7/charts/camunda-platform/templates/connectors/deployment.yaml#L54


      
          {{- if eq .Values.connectors.inbound.mode "disabled" }}
            - name: CAMUNDA_CONNECTOR_POLLING_ENABLED
              value: "false"
            - name: CAMUNDA_CONNECTOR_WEBHOOK_ENABLED
              value: "false"
          {{- end }}
          {{- if eq .Values.connectors.inbound.mode "credentials" }}
            - name: CAMUNDA_OPERATE_CLIENT_URL
              value: {{ include "camundaPlatform.operateURL" . | quote }}
            - name: CAMUNDA_OPERATE_CLIENT_USERNAME
              value: connectors
            - name: CAMUNDA_OPERATE_CLIENT_PASSWORD
              valueFrom:
                secretKeyRef:
                  name: {{ include "connectors.authCredentialsSecretName" . }}
                  key: connectors-secret
          {{- end }}
          {{- if and .Values.global.identity.auth.enabled (eq .Values.connectors.inbound.mode "oauth") }}
            - name: CAMUNDA_OPERATE_CLIENT_KEYCLOAK-TOKEN-URL
              value: {{ include "camundaPlatform.authIssuerBackendUrlTokenEndpoint" . | quote }}
            - name: CAMUNDA_OPERATE_CLIENT_CLIENT-ID

Any resolution for this.?

MohitSinghSolanki-A · September 5, 2024, 6:21am

Unable to authenticate due to missing Set-Cookie

Alex_Voloshyn · September 5, 2024, 9:43am

Can you share your helm values file?

Karthik_Bhat · September 5, 2024, 10:04am

Hey please find the attached values file.
values-sandbox.yaml (200.0 KB)

Karthik_Bhat · September 9, 2024, 11:07am

The cookie issue is resolved.
Secret was getting refreshed every time when connector pod was getting restarted,
I’ve set the value for connectors.inbound.auth.existingSecret.

Now I’m getting new issue which is,

2024-09-09T10:37:31.667Z ERROR 1 --- [   scheduling-1] i.camunda.common.http.DefaultHttpClient  : Failed POST with responseType class io.camunda.operate.model.SearchResult, parameterType class io.camunda.operate.model.ProcessDefinition, selector io.camunda.operate.model.SearchResult<io.camunda.operate.model.ProcessDefinition>, body io.camunda.operate.search.SearchQuery@70231f due to Response not successful: 403
2024-09-09T10:37:31.667Z ERROR 1 --- [   scheduling-1] i.c.c.r.i.i.ProcessDefinitionImporter    : Failed to import process definitions
io.camunda.common.exception.SdkException: io.camunda.common.exception.SdkException: Response not successful: 403
at io.camunda.common.http.DefaultHttpClient.post(DefaultHttpClient.java:162)	at io.camunda.operate.CamundaOperateClient.searchProcessDefinitionResults(CamundaOperateClient.java:46)	
at io.camunda.connector.runtime.inbound.importer.ProcessDefinitionSearch.query(ProcessDefinitionSearch.java:72)	
at io.camunda.connector.runtime.inbound.importer.ProcessDefinitionImporter.scheduleImport(ProcessDefinitionImporter.java:55)	
at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(Unknown Source)	at java.base/java.lang.reflect.Method.invoke(Unknown Source)

Is there anything from the permission side from operator side or open search side.?
I tried giving OWNER access for operate user, still it remains the same.
On open search side as well it has full access.

Thanks.