Skip to content

AD Bind user configuration #487

@hyd3l

Description

@hyd3l

Hi,
I'm using the tag 1.9.1 of the official kouncil docker image.

This is my docker-compose.yml :

networks:
  base-network:
    name: base-network
    external: true

services:
  kouncil:
    container_name: kouncil
    restart: on-failure
    image: consdata/kouncil:1.9.1
    ports:
      - 127.0.0.1:8083:8080
    volumes:
      - /opt/apps/kouncil/_data:/config/
    networks:
      - base-network
    logging:
      options:
        max-size: 50m

In the /opt/apps/kouncil/_data folder I added this configuration for Kouncil:

# /opt/apps/kouncil/_data/kouncil.yaml

kouncil:
  auth:
    active-provider: ldap
    ldap:
      provider-url: "ldaps://ad.domain.com"
      technical-user-name: "CN=KouncilBindUser,OU=Service Accounts,DC=ad,DC=domain,DC=com"
      technical-user-password: "secret"
      search-base: "DC=ad,DC=domain,DC=com"
      search-filter: "(|(memberOf=CN=KOUNCIL-GRP,OU=Group Members,OU=Security Groups,DC=ad,DC=domain,DC=com))"

I can't understand from the documentation how I can configure it so that the username provided is the "sAMAccountName" parameter
of Active Directory.
I'm also not so sure that the technical-user-name is actually being properly configured, I used the cn , in many other apps like Jenkins it usually works this way.

Thanks in advance

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions