Postman issues in Camunda 8.8 (self managed)

[Francesco1]

I installed Camunda 8.8 by downloading the docker-compose and then:

docker compose -f docker-compose-full.yaml up -d

I’m trying to test Camunda 8.8 new APIs in Postman, however, I don’t know what environment variables should I use in order to make the APIs work. I tryied by forking the environment “Local C8 Development“ and by setting the variables from there but I don’t know what to put as values, for example:

• authorizationServerUrl
• camundaApiAudience
• camundaApiClientId
• camundaApiClientSecret

[zee-bot]

Hi @Francesco1!

Great question about configuring Postman for your local Camunda 8.8 docker-compose setup. For the “Local C8 Development” environment in Postman, you’ll need to set the following environment variables based on your local Keycloak setup:

Environment Variables for Local Development

Here are the typical values for a standard Camunda 8.8 docker-compose setup:

• authorizationServerUrl: http://localhost:18080/auth/realms/camunda-platform/protocol/openid-connect/token
• camundaApiAudience: This depends on which API you’re calling:
  • For Tasklist API: tasklist-api
  • For Operate API: operate-api
  • For Zeebe API: zeebe-api
• camundaApiClientId: This depends on the component:
  • For Tasklist: tasklist
  • For Operate: operate
• camundaApiClientSecret: The default is usually XALaRPl5qwTEItdwCMiPS62nVpKs7dL7

How to Use These Values

1. First, get a Bearer token by making a POST request to the authorization server:

   • URL: http://localhost:18080/auth/realms/camunda-platform/protocol/openid-connect/token
   • Method: POST
   • Body (x-www-form-urlencoded):
     • client_id: tasklist (or the appropriate client for your API)
     • client_secret: XALaRPl5qwTEItdwCMiPS62nVpKs7dL7
     • grant_type: client_credentials
     • audience: tasklist-api (or the appropriate audience)

2. Use the returned access_token as a Bearer token in your API requests:

   Authorization: Bearer <access_token>
   

Verify Your Docker Compose Configuration

You can double-check these values by looking at the environment variables in your docker-compose-full.yaml file. Look for variables like:

• CAMUNDA_TASKLIST_IDENTITY_CLIENTID
• CAMUNDA_TASKLIST_IDENTITY_CLIENTSECRET
• CAMUNDA_TASKLIST_IDENTITY_AUDIENCE

If you’ve customized these values in your setup, use your custom values instead of the defaults.

References

• Camunda API REST Authentication Documentation
• Docker Compose Setup Guide

Let me know if you need help with any specific API or if you encounter any issues with the authentication!