meet docker-compose with existing kopano setup



  • Hi Felix,
    I’m trying to setup Meet with our existing kopano setup as backend. My docker host is of course NOT the mailserver host. I this possible? at the moment I get an error when a user tries to login:

    kopano_konnect_1    | time="2019-10-26T19:41:39Z" level=error msg="identifier failed to logon with backend" error="kc identifier backend logon error: failed to open unix socket: Get Connection timeout"
    

    of course socket is not available on the docker server.
    I’ve done 2 changes to the example meet from github

    1. .env file
    #KC-Backend
    KOPANO_SERVER_DEFAULT_URI=http://192.168.0.10:236
    KOPANO_SERVER_USERNAME=proxyuser
    KOPANO_SERVER_PASSWORD=myverysecrecpassword
    
    1. docker-compose.yml
          #- KONNECT_BACKEND=ldap
          - KONNECT_BACKEND=kc
    

    I’ve successfully conected to the samba-AD server with ldap-backend.
    There I can login, but can not see other users from AD.
    The example on github uses Openldap backend, to get AD to work one has to change two lines:

          - LDAP_LOGIN_ATTRIBUTE=sAMAccountName
          - LDAP_NAME_ATTRIBUTE=displayName
    
    

    It would be very nice, to have some more examples for existing setups.
    Thank you for any suggestions…
    Regards,
    Sebastian


  • Kopano

    Hi @segro,

    @segro said in meet docker-compose with existing kopano setup:

    I’ve done 2 changes to the example meet from github

    .env file

    Just adding more environment variables to the env file does not mean that the started containers will directly be aware of these. Are these listed when exec’ing into the container and calling env? What is the error message after you have set these variables?

    @segro said in meet docker-compose with existing kopano setup:

    The example on github uses Openldap backend, to get AD to work one has to change two lines:

    I can imagine with an additional question in setup.sh the .env file could be auto filled with these values. Would you be interested in working on this and creating a pull request? If yes then I can provide some further pointers.


  • Kopano

    @segro said in meet docker-compose with existing kopano setup:

    error=“kc identifier backend logon error: failed to open unix socket: Get Connection timeout”

    This error message indicates that your setting of KOPANO_SERVER_DEFAULT_URI=http://192.168.0.10:236 has no effect (since that error message is from the unix socket connector).


Log in to reply