How to authenticate tasklist and other components of camunda 8 using identity

shaikhm357 · November 10, 2022, 4:58am

Hi everyone,
I am new to camunda
I wanted to change the login credential of say tasklist (id: demo pw: demo) to something else like id: foo pw: bar and I wanted to do this using the identity component of camunda8
I have done with setup of identity and keycloak and I have created one user in keycloak and that user is reflecting in “user” tab of identity too. but I am unable to login with that user.
any help is appreciated.
Thanks in advance

Hafflgav · November 14, 2022, 11:54am

Hey @shaikhm357,
I remember that there once was a limitation in the “non-enterprise” offering of Camunda 8 self-managed, where you could not set any other credentials.
Not sure whether this is still the case. Tagging @ben.sheppard - he for sure knows more about this than I do.

Could you share some more insights on how you configured keycloak and identiy?
Thanks a lot in advance!

Best,
Thomas

Hafflgav · November 14, 2022, 11:56am

Quick add-on from our docu:
Have you seen these pages?

It says:

Creating a user in Identity is not currently supported. To create a user, see Keycloak’s documentation on creating a user.

That might be the solution to your problem

shaikhm357 · November 24, 2022, 9:09am

@Hafflgav
thanks for your reply.
there was a problem with my .yml file.
this link helped me.

github.com

camunda/camunda-platform/blob/8.1.1/docker-compose.yaml

# While the Docker images themselves are supported for production usage,
# this docker-compose.yaml is designed to be used by developers to run
# an environment locally. It is not designed to be used in production.
# We recommend to use Kubernetes in production with our Helm Charts:
# https://docs.camunda.io/docs/self-managed/platform-deployment/kubernetes-helm/
# For local development, we recommend using KIND instead of `docker-compose`:
# https://docs.camunda.io/docs/self-managed/platform-deployment/kubernetes-helm/#installing-the-camunda-helm-chart-locally-using-kind

# This is a full configuration with Zeebe, Operate, Tasklist, Optimize, Identity, Keycloak, and Elasticsearch
# See docker-compose-core.yml for a lightweight configuration that does not include Optimize, Identity, and Keycloak.

services:

  zeebe: # https://docs.camunda.io/docs/self-managed/platform-deployment/docker/#zeebe
    image: camunda/zeebe:${CAMUNDA_PLATFORM_VERSION:-8.1.1}
    container_name: zeebe
    ports:
      - "26500:26500"
      - "9600:9600"
    environment: # https://docs.camunda.io/docs/self-managed/zeebe-deployment/configuration/environment-variables/

This file has been truncated. show original

ben.sheppard · November 25, 2022, 9:51am

Hi @shaikhm357!

I’m sorry for not responding sooner. I can see that the link shared by @Hafflgav helped which is brilliant! I wanted to offer a second solution to the problem although it is only applicable in certain scenarios such as testing and not designed for production situations.

Along side the creation of users in Keycloak you are also able to define a user via configuration variables, for example when we are developing for the Identity component we will use something such as the following to create a test user:

KEYCLOAK_USERS_0_FIRST_NAME=Bark
KEYCLOAK_USERS_0_LAST_NAME=Barkins
KEYCLOAK_USERS_0_USERNAME=myusername
KEYCLOAK_USERS_0_PASSWORD=mypassword
KEYCLOAK_USERS_0_ROLES_0=Identity

As I say, it may not be appropriate to your needs but I wanted to mention it!

Ben