Ad Widget

Collapse

docker frontend - ldap / ldaps info persistent ?

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • ramoneastral
    Member
    • Feb 2017
    • 33

    #1

    docker frontend - ldap / ldaps info persistent ?

    i have a working environment incl debian package for the front end.
    ldap(s) works fine !

    i now want to move the frontend to docker .
    which works fine if you use a local user :-)
    once you try to use the ldap user , the docker frontend will state : cannot bind to ldap

    there seem to some bits and pieces on google which point to /usr/share/zabbix/include/classes/ldap/CLdap.conf.

    but there is nothing new.
    taking a local user and resaving the ldap config in the frontend will make the docker frontend also work with ldap.

    question :
    is ldap "done" via php / webfrontend ? or is the zabbix server process doing that ldap connection / validation ?
    if you use the web frontend to configure the ldap stuff , where is this information stored ? (inside docker image ? , database ?)

    how does that relate to docker webfrontend;
    do you need to mount files or volumes to make an ldap / docker persistent ?
    which files need to be mounted ?
    especially which files need to be considered when doing ldapS(ecure) ? (having internal CA being used on AD...)

    is json API effected in any way with docker frontend ?
Working...