Static Users Configuration for Test/Development

Test Deployments Only

This configuration uses static username/password credentials stored directly in Dex configuration. This is only suitable for test and development environments. For production deployments, always use an external OIDC provider as described in the Installation Process.

For test and development purposes, you can configure Dex with static users that authenticate using username and password:

pharia-iam:
  config:
    # -- Email address of the user who should receive admin privileges
    #    This email must match one of the static users defined in the Dex configuration below
    adminEmail: "max.mustermann@your-company-doman.com"

zitadel:
  enabled: false

dex:
  enabled: true
  
  config:
    # Enable static password authentication for test purposes
    enablePasswordDB: true
    
    # Define static users (for testing only)
    staticPasswords:
    - email: "max.mustermann@your-company-doman.com"
      # bcrypt hash of the string "password" (generate your own using: htpasswd -bnBC 10 "" <password> | tr -d ':\n')
      hash: "$2y$10$JSRfGzwQi5KJpTEQHKrfzeKmIQd0EaQtHUpSlGuzXbT/GX5.Z.S3W"
      username: "admin"
      userID: "08a8684b-db88-4b73-90a9-3cd1661f5466"
    - email: "test@example.com"
      hash: "$2y$10$wO7.IgbzMb2pqvgsTMTDs.NC77y1gO/izyh/gJIyLbPNNr1lEjNIC"
      username: "testuser"
      userID: "18b8684b-db88-4b73-90a9-3cd1661f5477"

# For test deployments: Use included PostgreSQL database
dexPostgresql:
  enabled: true

Important Notes for Static User Configuration

• The password must be bcrypt-hashed. Generate a hash using: htpasswd -bnBC 10 "" <your-password> | tr -d ':\n'
• Each user needs a unique userID (e.g. use a UUID generator)
• The email address in adminEmail must match one of the static users' email addresses to grant admin privileges
• Replace the example emails, usernames, and password hashes with your own values
• This configuration should never be used in production environments
• Static users cannot be managed through the UI; you must update the Helm configuration to add/modify users