starred/papermerge

Fork 0

mirror of https://github.com/ciur/papermerge.git synced 2026-04-25 12:05:58 +03:00

[GH-ISSUE #94] LDAP/External Authentication Support #73

New issue

Closed

opened 2026-02-25 21:31:08 +03:00 by kerem · 9 comments

kerem commented

2026-02-25 21:31:08 +03:00

Owner

Originally created by @Diablofan on GitHub (Aug 22, 2020).
Original GitHub issue: https://github.com/ciur/papermerge/issues/94

Originally assigned to: @ciur on GitHub.

I was wondering if external authentication support, like LDAP, could be added in.

It would be nice if it were supported as it would allow me to delegate out user logins without having to set them up in the app and make sure they are constantly in sync (say with password changes).

It would also allow me to use the same authentication mechanism that all the other applications I have installed on my server are also using.

I'm sure this also would be beneficial for larger orgs since they would probably want some sort of directory based authentication like LDAP or Active Directory, again, for the same reasons I listed above.

Originally created by @Diablofan on GitHub (Aug 22, 2020). Original GitHub issue: https://github.com/ciur/papermerge/issues/94 Originally assigned to: @ciur on GitHub. I was wondering if external authentication support, like LDAP, could be added in. It would be nice if it were supported as it would allow me to delegate out user logins without having to set them up in the app and make sure they are constantly in sync (say with password changes). It would also allow me to use the same authentication mechanism that all the other applications I have installed on my server are also using. I'm sure this also would be beneficial for larger orgs since they would probably want some sort of directory based authentication like LDAP or Active Directory, again, for the same reasons I listed above.

kerem

2026-02-25 21:31:08 +03:00

closed this issue
added the
feature request
label

kerem commented

2026-02-25 21:31:09 +03:00

Author

Owner

@ciur commented on GitHub (Aug 22, 2020):

Yes! it would be added, and external authentication has high priority.
I will add this feature in queue and prioritize it for next 1.5 release.

I'm sure this also would be beneficial for larger orgs since they would probably want some sort of directory based authentication like LDAP or Active Directory, again, for the same reasons I listed above.

I absolutely agree!

Thank you for your time and opening a feature request!

@ciur commented on GitHub (Aug 22, 2020): Yes! it would be added, and external authentication has high priority. I will add this feature in queue and prioritize it for next 1.5 release. > I'm sure this also would be beneficial for larger orgs since they would probably want some sort of directory based authentication like LDAP or Active Directory, again, for the same reasons I listed above. I absolutely agree! Thank you for your time and opening a feature request!

kerem commented

2026-02-25 21:31:09 +03:00

Author

Owner

@ciur commented on GitHub (Oct 2, 2020):

Planned as part of 1.6.0 release.

@ciur commented on GitHub (Oct 2, 2020): Planned as part of 1.6.0 release.

kerem commented

2026-02-25 21:31:09 +03:00

Author

Owner

@Baton4986 commented on GitHub (Mar 15, 2021):

Planned as part of 1.6.0 release.

hi, any news about this? i did not find it in changelog, so when will it be available?

@Baton4986 commented on GitHub (Mar 15, 2021): > Planned as part of 1.6.0 release. hi, any news about this? i did not find it in changelog, so when will it be available?

kerem commented

2026-02-25 21:31:09 +03:00

Author

Owner

@Baton4986 commented on GitHub (Oct 14, 2021):

is there any chance to get this forward like donation?

@Baton4986 commented on GitHub (Oct 14, 2021): is there any chance to get this forward like donation?

kerem commented

2026-02-25 21:31:09 +03:00

Author

Owner

@ciur commented on GitHub (Oct 15, 2021):

is there any chance to get this forward like donation?

@ramon-kramer, sure. #231 details on different ways to support the project.

Please, keep in mind that support for LDAP authentication will be implemented as part of 2.2.0 version which will be released following year (i.e. 2022).

@ciur commented on GitHub (Oct 15, 2021): > is there any chance to get this forward like donation? @ramon-kramer, sure. #231 details on different ways to support the project. Please, keep in mind that support for LDAP authentication will be implemented as part of 2.2.0 version which will be released following year (i.e. 2022).

kerem commented

2026-02-25 21:31:09 +03:00

Author

Owner

@phinnay commented on GitHub (Apr 7, 2022):

Bumping the thread now that it's 2022, is there an ETA for this feature and will donations help? Loving Papermerge!!!

@phinnay commented on GitHub (Apr 7, 2022): Bumping the thread now that it's 2022, is there an ETA for this feature and will donations help? Loving Papermerge!!!

kerem commented

2026-02-25 21:31:09 +03:00

Author

Owner

@ciur commented on GitHub (Apr 8, 2022):

@phinnay, donations are welcome, but they won't speed development 😄

Once you brought up the topic, let me say couple of words here. I am in chatty mode 😄

Last stable release was out exactly one year ago. So, it makes perfect sense to ask, why releasing next version takes more than a year (in this agile world, where two weeks release cycle is norm) ?

It is because I have long term plans for Papermerge. In order for software to be long term sustainable it needs a solid architectural foundation. However, version 2.0, had serious design issues. Just to mention one problem - the frontend code.
The frontend code was ever growing mess...
For relatively young application, javascript code was seriously problematic.
I instead of continuing applying minor design fixes here and there - I decided to completely rewrite frontend part.

It took me a lot of time to figure out how to get done the frontend part "right way". "Right" code is application code which is relatively well organized, and regardless how much application increases in complexity - code is still easy to read and make sense of.

Backend code had serious changes as well, but in overall did not change much.

In short, it will take some time until 2.1, and it will take even more time until LDAP authentication will be out (as part of 2.2).
Building quality applications needs time and patients and I assure you it is worth it.

Off topic, but I cannot help and not to show you what I am playing with currently:

But the real jewel is the frontend code itself.
Look at this beauty!

Also, see my last update

@ciur commented on GitHub (Apr 8, 2022): @phinnay, donations are welcome, but they won't speed development :smile: Once you brought up the topic, let me say couple of words here. I am in chatty mode :smile: Last stable release was out exactly one year ago. So, it makes perfect sense to ask, why releasing next version takes more than a year (in this agile world, where two weeks release cycle is norm) ? It is because I have long term plans for Papermerge. In order for software to be long term sustainable it needs a solid architectural foundation. However, version 2.0, had serious design issues. Just to mention one problem - the frontend code. The frontend code was ever growing mess... For relatively young application, javascript code was seriously problematic. I instead of continuing applying minor design fixes here and there - I decided to completely rewrite frontend part. It took me a lot of time to figure out how to get done the frontend part "right way". "Right" code is application code which is relatively well organized, and regardless how much application increases in complexity - code is still easy to read and make sense of. Backend code had serious changes as well, but in overall did not change much. In short, it will take some time until 2.1, and it will take even more time until LDAP authentication will be out (as part of 2.2). Building quality applications needs time and patients and I assure you it is worth it. Off topic, but I cannot help and not to show you what I am playing with currently: ![quick-preview-work-in-progress](https://user-images.githubusercontent.com/24827601/162375678-5c771982-9fa6-463a-b286-fa70fdb3f9b1.gif) But the real jewel is the frontend code itself. [Look at this beauty](https://github.com/papermerge/papermerge.js)! Also, see [my last update](https://github.com/ciur/papermerge/issues/435#issuecomment-1087896698)

kerem commented

2026-02-25 21:31:09 +03:00

Author

Owner

@ciur commented on GitHub (May 14, 2024):

Papermerge 3.2 has OIDC (OpenID connect) support. I've tested it with keycloak and it works. Keycloak has user federation i.e. loading your users from ldap source (to be exact sync with ldap). What you ca do, is configure papermerge with keycloak and let keyloak handle ldap part.

Doc link: https://docs.papermerge.io/3.2/sso/oidc/keycloak/

@ciur commented on GitHub (May 14, 2024): Papermerge 3.2 has OIDC (OpenID connect) support. I've tested it with keycloak and it works. Keycloak has user federation i.e. loading your users from ldap source (to be exact sync with ldap). What you ca do, is configure papermerge with keycloak and let keyloak handle ldap part. Doc link: https://docs.papermerge.io/3.2/sso/oidc/keycloak/

kerem commented

2026-02-25 21:31:09 +03:00

Author

Owner

@ciur commented on GitHub (May 14, 2024):

I am closing this ticket as feature is already landed in 3.2 (via keycloak/OIDC support).

@ciur commented on GitHub (May 14, 2024): Papermerge 3.2 has OIDC (OpenID connect) support. I've tested it with keycloak and it works. Keycloak has user federation i.e. loading your users from ldap source (to be exact sync with ldap). What you ca do, is configure papermerge with keycloak and let keyloak handle ldap part. I am closing this ticket as feature is already landed in 3.2 (via keycloak/OIDC support).

kerem referenced this issue

2026-02-25 21:32:11 +03:00

[PR #73] [MERGED] Add Meta class and ordering to Page model #541