Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Search
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

Cloudron Forum

Apps | Demo | Docs | Install
  1. Cloudron Forum
  2. Matomo
  3. Error "Could not find LDAP password for user" when logging into Matomo

Error "Could not find LDAP password for user" when logging into Matomo

Scheduled Pinned Locked Moved Solved Matomo
15 Posts 2 Posters 1.5k Views 2 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • girishG girish

    Our LDAP is like this:

    [LoginLdap]
    servers[] = "cloudron"
    ldap_user_id_field = "username"
    ldap_last_name_field = "sn"
    ldap_first_name_field = "givenName"
    ldap_mail_field = "mail"
    ldap_alias_field = "cn"
    use_ldap_for_authentication = 1
    new_user_default_sites_view_access = "all"
    synchronize_users_after_login = 1
    
    
    d19dotcaD Offline
    d19dotcaD Offline
    d19dotca
    wrote on last edited by d19dotca
    #5

    @girish Seems my config is the same (though oddly my "servers" field is at the bottom).

    [LoginLdap]
    ldap_user_id_field = "username"
    ldap_last_name_field = "sn"
    ldap_first_name_field = "givenName"
    ldap_mail_field = "mail"
    ldap_alias_field = "cn"
    use_ldap_for_authentication = 1
    new_user_default_sites_view_access = "all"
    synchronize_users_after_login = "1"
    servers[] = "cloudron"
    

    Here's the screenshot I see every time I login:

    c0eb1184-3885-484f-be74-549b6b72fc6a-image.png

    --
    Dustin Dauncey
    www.d19.ca

    girishG 1 Reply Last reply
    0
    • d19dotcaD d19dotca

      @girish Seems my config is the same (though oddly my "servers" field is at the bottom).

      [LoginLdap]
      ldap_user_id_field = "username"
      ldap_last_name_field = "sn"
      ldap_first_name_field = "givenName"
      ldap_mail_field = "mail"
      ldap_alias_field = "cn"
      use_ldap_for_authentication = 1
      new_user_default_sites_view_access = "all"
      synchronize_users_after_login = "1"
      servers[] = "cloudron"
      

      Here's the screenshot I see every time I login:

      c0eb1184-3885-484f-be74-549b6b72fc6a-image.png

      girishG Offline
      girishG Offline
      girish
      Staff
      wrote on last edited by
      #6

      @d19dotca strange, I can't reproduce this on a new install either. I guess we need to wait for https://github.com/matomo-org/plugin-LoginLdap/issues/204 to be resolved or something . Cloudron LDAP server does not expose LDAP password for security reasons as well.

      d19dotcaD 1 Reply Last reply
      1
      • girishG girish

        @d19dotca strange, I can't reproduce this on a new install either. I guess we need to wait for https://github.com/matomo-org/plugin-LoginLdap/issues/204 to be resolved or something . Cloudron LDAP server does not expose LDAP password for security reasons as well.

        d19dotcaD Offline
        d19dotcaD Offline
        d19dotca
        wrote on last edited by
        #7

        @girish If I understand that GitHub issue correctly though it seems one suggestion was to switch synchronize_users_after_login to a value of 0, however that isn't working for me because every time I restart Matomo it seems to override any config I put in there. Is this intended behaviour or do you think it should be changed? Essentially this limit in the package seems to prevent me from even testing that proposed solution from the GitHub issue.

        --
        Dustin Dauncey
        www.d19.ca

        girishG 1 Reply Last reply
        0
        • d19dotcaD d19dotca

          @girish If I understand that GitHub issue correctly though it seems one suggestion was to switch synchronize_users_after_login to a value of 0, however that isn't working for me because every time I restart Matomo it seems to override any config I put in there. Is this intended behaviour or do you think it should be changed? Essentially this limit in the package seems to prevent me from even testing that proposed solution from the GitHub issue.

          girishG Offline
          girishG Offline
          girish
          Staff
          wrote on last edited by
          #8

          @d19dotca Maybe you can put the app into Repair mode. Then, you can edit /app/pkg/start.sh (the line where it sets that config variable to 0) and then start the app by running /app/pkg/start.sh .

          d19dotcaD 1 Reply Last reply
          0
          • girishG girish

            @d19dotca Maybe you can put the app into Repair mode. Then, you can edit /app/pkg/start.sh (the line where it sets that config variable to 0) and then start the app by running /app/pkg/start.sh .

            d19dotcaD Offline
            d19dotcaD Offline
            d19dotca
            wrote on last edited by d19dotca
            #9

            @girish Ah okay, interesting, I can try that.

            One latest attempt (haven't tried the repair mode yet though) as it was recommended upstream to change "warning" to "debug" on one of their lines of code in a particular file, but doesn't seem to save my changes from that either after restarting the app. I'm confused though because I thought items in /app/data were usually safe from overrides?

            There will be a file called UserMapper.php in /path/to/your/matomo/plugins/plugins/LoginLdap/LdapInterop/UserMapper.php
            You need to search for word warning which will look something like this $this->logger->warning just replace the warning word with debug
            

            --
            Dustin Dauncey
            www.d19.ca

            girishG 1 Reply Last reply
            0
            • d19dotcaD d19dotca

              @girish Ah okay, interesting, I can try that.

              One latest attempt (haven't tried the repair mode yet though) as it was recommended upstream to change "warning" to "debug" on one of their lines of code in a particular file, but doesn't seem to save my changes from that either after restarting the app. I'm confused though because I thought items in /app/data were usually safe from overrides?

              There will be a file called UserMapper.php in /path/to/your/matomo/plugins/plugins/LoginLdap/LdapInterop/UserMapper.php
              You need to search for word warning which will look something like this $this->logger->warning just replace the warning word with debug
              
              girishG Offline
              girishG Offline
              girish
              Staff
              wrote on last edited by
              #10

              @d19dotca I think LDAP plugin is overwritten on restart (this plugin is maintained by the package itself, so you don't have to update LDAP plugin manually). Are you restarting the app? If so, do not restart the app.

              d19dotcaD 1 Reply Last reply
              0
              • girishG girish

                @d19dotca I think LDAP plugin is overwritten on restart (this plugin is maintained by the package itself, so you don't have to update LDAP plugin manually). Are you restarting the app? If so, do not restart the app.

                d19dotcaD Offline
                d19dotcaD Offline
                d19dotca
                wrote on last edited by
                #11

                @girish Yeah I was restarting the app after making the changes, makes sense why that isn't saving then if the package itself is overwriting the LDAP-related config section and plugin.

                --
                Dustin Dauncey
                www.d19.ca

                girishG 1 Reply Last reply
                0
                • d19dotcaD d19dotca

                  @girish Yeah I was restarting the app after making the changes, makes sense why that isn't saving then if the package itself is overwriting the LDAP-related config section and plugin.

                  girishG Offline
                  girishG Offline
                  girish
                  Staff
                  wrote on last edited by
                  #12

                  @d19dotca Did that work out? Would be good to get this sorted out upstream.

                  I am going to give this another shot now to see why new instances don't hit this code path.

                  1 Reply Last reply
                  0
                  • girishG Offline
                    girishG Offline
                    girish
                    Staff
                    wrote on last edited by
                    #13

                    I have to say I debugged this a lot but can never get that error message to show! I enabled all sorts of syncing in the configs, but that error message never shows.

                    d19dotcaD 1 Reply Last reply
                    0
                    • girishG girish

                      I have to say I debugged this a lot but can never get that error message to show! I enabled all sorts of syncing in the configs, but that error message never shows.

                      d19dotcaD Offline
                      d19dotcaD Offline
                      d19dotca
                      wrote on last edited by
                      #14

                      @girish thanks for trying so hard on this, Girish! It’s definitely an odd issue but thankfully doesn’t seem to have an impact beyond the nagging window when logging in each time. I can ignore it for now but I also haven’t had a chance to test with that repair mode so I may try that soon too.

                      --
                      Dustin Dauncey
                      www.d19.ca

                      1 Reply Last reply
                      0
                      • d19dotcaD Offline
                        d19dotcaD Offline
                        d19dotca
                        wrote on last edited by
                        #15

                        Seems the latest release fixed the issue, I presume because they modified the plugin code for the LDAP access to Matomo. 🙂 Can mark this as Solved I think.

                        --
                        Dustin Dauncey
                        www.d19.ca

                        1 Reply Last reply
                        1
                        • girishG girish marked this topic as a question on
                        • girishG girish has marked this topic as solved on
                        Reply
                        • Reply as topic
                        Log in to reply
                        • Oldest to Newest
                        • Newest to Oldest
                        • Most Votes


                        • Login

                        • Don't have an account? Register

                        • Login or register to search.
                        • First post
                          Last post
                        0
                        • Categories
                        • Recent
                        • Tags
                        • Popular
                        • Bookmarks
                        • Search