Centralized account management missing (Active Directory / LDAP) #379

Closed
opened 2026-02-19 23:07:39 -05:00 by deekerman · 7 comments
Owner

Originally created by @Expro on GitHub (Aug 11, 2020).

Originally assigned to: @lastzero on GitHub.

Any plans to add support for Active Directory, LDAP or other centralized account management options?

Originally created by @Expro on GitHub (Aug 11, 2020). Originally assigned to: @lastzero on GitHub. Any plans to add support for Active Directory, LDAP or other centralized account management options?
deekerman 2026-02-19 23:07:39 -05:00
  • closed this issue
  • added the
    question
    label
Author
Owner

@lastzero commented on GitHub (Aug 11, 2020):

Maybe in a future "pro" release or commercial add-on as we expect this to be (primarily) used in business environments. It's not our goal to provide a free enterprise solution.

@lastzero commented on GitHub (Aug 11, 2020): Maybe in a future "pro" release or commercial add-on as we expect this to be (primarily) used in business environments. It's not our goal to provide a free enterprise solution.
Author
Owner

@Expro commented on GitHub (Aug 11, 2020):

Well, to be honest, using LDAP / AD got nothing to do with business or enterprise - with multiple community driven open source projects running, creating local accounts on every one of them quickly gets out of hand. That's why all popular open source projects supports it, even in community editions, despite having paid support options (to name few: Nextcloud / OwnCloud, Jellyfin / Emby, Organizr, pfSense, FreeNAS).

@Expro commented on GitHub (Aug 11, 2020): Well, to be honest, using LDAP / AD got nothing to do with business or enterprise - with multiple community driven open source projects running, creating local accounts on every one of them quickly gets out of hand. That's why all popular open source projects supports it, even in community editions, despite having paid support options (to name few: Nextcloud / OwnCloud, Jellyfin / Emby, Organizr, pfSense, FreeNAS).
Author
Owner

@lastzero commented on GitHub (Aug 11, 2020):

We'll get in touch with the community once we are ready to implement new features. They will be implemented based on demand / perceived value. So if enough users need this, we'll do it. However, we can't continue to provide everything for free, especially advanced features that could be used in enterprise environments. Not saying you would do this. Thanks for your feedback!

@lastzero commented on GitHub (Aug 11, 2020): We'll get in touch with the community once we are ready to implement new features. They will be implemented based on demand / perceived value. So if enough users need this, we'll do it. However, we can't continue to provide everything for free, especially advanced features that could be used in enterprise environments. Not saying you would do this. Thanks for your feedback!
Author
Owner

@lastzero commented on GitHub (Aug 11, 2020):

See also Multi-User Photo Gallery with private and shared photos/albums #98

@lastzero commented on GitHub (Aug 11, 2020): See also [Multi-User Photo Gallery with private and shared photos/albums #98](https://github.com/photoprism/photoprism/issues/98)
Author
Owner

@lastzero commented on GitHub (Aug 11, 2020):

I assumed proper "centralized account management" includes support for multiple, completely independent user accounts as discussed in #98. Limiting LDAP support to a single account will be much easier.

If someone has time to implement this, we'll of course merge it given it is well tested and doesn't introduce security or performance issues. Since we don't have a huge team of developers, we're very careful with introducing complexity to the project. That includes features with potentially high security or performance impact and high testing effort that only very few users actually need / use. This in fact was the first time someone asks for LDAP. Should this become a very common use case for the community edition, we can absolutely put it on the todo list.

@lastzero commented on GitHub (Aug 11, 2020): I assumed proper "centralized account management" includes support for multiple, completely independent user accounts as discussed in #98. Limiting LDAP support to a single account will be much easier. If someone has time to implement this, we'll of course merge it given it is well tested and doesn't introduce security or performance issues. Since we don't have a huge team of developers, we're very careful with introducing complexity to the project. That includes features with potentially high security or performance impact and high testing effort that only very few users actually need / use. This in fact was the first time someone asks for LDAP. Should this become a very common use case for the community edition, we can absolutely put it on the todo list.
Author
Owner

@tigattack commented on GitHub (Nov 12, 2020):

I understand you don't want to implement a "free enterprise solution", but could you not go with a pricing scheme of "free for home users" with a limitation of, for example, up to 15 users, including "enterprise" features such as LDAP authentication, which would be really appreciated by many, I am sure.

Businesses would then pay for higher plans as they'd have more users, and you'd get the licensing revenue you need whilst keeping home users happy.

@tigattack commented on GitHub (Nov 12, 2020): I understand you don't want to implement a "free enterprise solution", but could you not go with a pricing scheme of "free for home users" with a limitation of, for example, up to 15 users, including "enterprise" features such as LDAP authentication, which would be really appreciated by many, I am sure. Businesses would then pay for higher plans as they'd have more users, and you'd get the licensing revenue you need whilst keeping home users happy.
Author
Owner

@lastzero commented on GitHub (Nov 12, 2020):

We're working something out right now and will move on from there once we have LDAP done :)

@lastzero commented on GitHub (Nov 12, 2020): We're working something out right now and will move on from there once we have LDAP done :)
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/photoprism#379
No description provided.