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. Nextcloud
  3. LDAP: Login with username is not possible anymore

LDAP: Login with username is not possible anymore

Scheduled Pinned Locked Moved Solved Nextcloud
7 Posts 3 Posters 555 Views 3 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.
  • C Offline
    C Offline
    ctrl
    wrote on last edited by
    #1

    Hello Team,

    out of a sudden it is not possible to login to Nextcloud via username. It still works with the e-mail address. If I try to check a username in the LDAP / AD integration -> Login Attributes section then Nextcloud returns the following error message:

    User not found. Please check your login attributes and username. Effective filter (to copy-and-paste for command-line validation):
    (&(&(|(objectclass=user)))(|(uid=someusername)(|(mailPrimaryAddress=someusername)(mail=someusername))))
    

    If I check the email addess then Nextcloud returns a User found and settings verified. message. In contrast the database user admin is still able to login via username.

    I already doublechecked the userconfig inside my.cloudron but I didn't stumble upon any specific misconfiguration. Could someone please point me into the right direction?

    Kind regards

    1 Reply Last reply
    0
    • nebulonN Offline
      nebulonN Offline
      nebulon
      Staff
      wrote on last edited by
      #2

      I do wonder where that filter is coming from in your case. Cloudron should set it (and also reset it during app restart) to:

      (&(objectclass=user)(|(username=%uid)(mail=%uid)))
      
      1 Reply Last reply
      0
      • C Offline
        C Offline
        ctrl
        wrote on last edited by ctrl
        #3

        I tried your idea to simply restart the app which solved the issue. 😄
        Nevertheless I can't reproduce what caused the problem in first place - also I'm not able to tell how the filter changed.

        Thank you very much for your quick support!

        1 Reply Last reply
        0
        • nebulonN Offline
          nebulonN Offline
          nebulon
          Staff
          wrote on last edited by
          #4

          Yeah ideally to prevent such changes of settings, we would be able to hide that UI within the nextcloud settings panel, but I don't see how that can be done.

          murgeroM 1 Reply Last reply
          0
          • nebulonN nebulon

            Yeah ideally to prevent such changes of settings, we would be able to hide that UI within the nextcloud settings panel, but I don't see how that can be done.

            murgeroM Offline
            murgeroM Offline
            murgero
            App Dev
            wrote on last edited by
            #5

            @nebulon Custom plugin to hide it. I can write the plugin later and test then just include the plugin with the app.

            --
            https://urgero.org
            ~ Professional Nerd. Freelance Programmer. ~

            1 Reply Last reply
            0
            • nebulonN Offline
              nebulonN Offline
              nebulon
              Staff
              wrote on last edited by
              #6

              Given our experience with Nextcloud plugin handling, I would rather not want to maintain such a plugin actually. Ideally the ldap plugin itself (which is at least part of the core package) would have a flag to show/hide the UI. Not sure if this would get any traction upstream, but if you want to get your hands into a custom plugin, maybe you could roughly check if such a flag would be possible to add?

              murgeroM 1 Reply Last reply
              1
              • nebulonN nebulon

                Given our experience with Nextcloud plugin handling, I would rather not want to maintain such a plugin actually. Ideally the ldap plugin itself (which is at least part of the core package) would have a flag to show/hide the UI. Not sure if this would get any traction upstream, but if you want to get your hands into a custom plugin, maybe you could roughly check if such a flag would be possible to add?

                murgeroM Offline
                murgeroM Offline
                murgero
                App Dev
                wrote on last edited by
                #7

                @nebulon hmmm yeah I could see the potential for extra work, but as long as the css for the ldap plugin doesn't change too much I'd imagine it would a "build it once and forget about it" situation.

                That said, adding the option to disable the ldap UI for non-admins is a no-brainer I'm sure for Nextcloud programmers.

                --
                https://urgero.org
                ~ Professional Nerd. Freelance Programmer. ~

                1 Reply Last reply
                0
                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