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


Navigation

    Cloudron Forum

    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular

    Extra fields in LDAP

    Feature Requests
    directory ldap
    7
    13
    94
    Loading More Posts
    • 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.
    • girish
      girish Staff last edited by

      I do like the idea of making the central user management more 'complete'. Maybe this is more for apps outside cloudron than the ones we have packaged so far.

      1 Reply Last reply Reply Quote 4
      • marcusquinn
        marcusquinn last edited by marcusquinn

        Phone number(s) at least is handy for Mattermost and other apps where you can lookup by phone number(s), and some that use it as a 2FA option.

        Lonk 1 Reply Last reply Reply Quote 3
        • Lonk
          Lonk @marcusquinn last edited by

          @marcusquinn We can use this thread to try to decide what fields make the most sense for whenever we want to add this feature to make the Cloudron directory more fleshed out.

          1 Reply Last reply Reply Quote 1
          • yusf
            yusf last edited by yusf

            For app maintenance reasons it might be reasonable to predefine a bunch of fields but they way I imagined it was that every Cloudron admin would be able to extend the LDAP user database with more custom fields, each to their liking. At most Cloudron would provide field types for limiting input.

            This way it would be up to the admins to integrate the additional information into the apps, as app compatibility and use case could vary drastically.

            Lonk 1 Reply Last reply Reply Quote 1
            • Lonk
              Lonk @yusf last edited by

              @yusf said in Extra fields in LDAP:

              For app maintenance reasons it might be reasonable to predefine a bunch of fields but they way I imagined it was that every Cloudron admin would be able to extend the LDAP user database with more custom fields, each to their liking. At most Cloudron would provide field types for limiting input.

              This way it would be up to the admins to integrate the additional information into the apps, as app compatibility and use case could vary drastically.

              I love that, making it user customizable. Is that feasible, you people that know more about LDAP than I do?

              1 Reply Last reply Reply Quote 0
              • mehdi
                mehdi App Dev last edited by

                The problem would not be so much on the LDAP side than on the app side : for a lot of apps, the LDAP config is overriden by cloudron on start to be set to the normal LDAP cloudron config, so I'm not sure how you could use such fields in the apps if they're not standard on Cloudron.

                1 Reply Last reply Reply Quote 0
                • nebulon
                  nebulon Staff last edited by

                  From a LDAP server perspective, it would be indeed quite easy to add more and even custom fields, however as @mehdi pointed out, this all comes down to integration with the apps. For example https://docs.bmc.com/docs/fpsc121/ldap-attributes-and-associated-fields-495323340.html holds a list of common attributes, which also are common on ActiveDirectory as far as I have seen. But looking at apps, I have not seen too many supporting them. So in order to not end up in some kind of mess, where we have to keep on patching upstream apps, I still kinda miss a collection of real use-cases. The phonenumber for Mattermost is one such use-case, but that can be also solved without custom fields.

                  Maybe @luckow can chime in here as well, since he has more experience with AD integration within organizations?

                  fbartels Lonk 2 Replies Last reply Reply Quote 0
                  • fbartels
                    fbartels App Dev @nebulon last edited by

                    @nebulon said in Extra fields in LDAP:

                    The phonenumber for Mattermost is one such use-case, but that can be also solved without custom fields.

                    this also does not take into account that the free team edition of Mattermost (as packaged in Cloudron) does not use ldap at all.

                    nebulon 1 Reply Last reply Reply Quote 2
                    • nebulon
                      nebulon Staff @fbartels last edited by

                      @fbartels that is a valid point! 😉

                      1 Reply Last reply Reply Quote 2
                      • Lonk
                        Lonk @nebulon last edited by

                        @nebulon said in Extra fields in LDAP:

                        The phonenumber for Mattermost is one such use-case, but that can be also solved without custom fields.

                        Assuming there might be a need for this in the future - what was the solution you thought of?

                        Also, even if app's don't use the fields, just having the Cloudron User directory more fleshed out might be a good thing for reference sake.

                        1 Reply Last reply Reply Quote 1
                        • First post
                          Last post