[GH-ISSUE #548] Papermerge 3.0 Status #425

New issue

Closed

opened 2026-02-25 21:31:54 +03:00 by kerem · 1 comment

kerem commented

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

Owner

Originally created by @ciur on GitHub (May 20, 2023).
Original GitHub issue: https://github.com/ciur/papermerge/issues/548

Originally assigned to: @ciur on GitHub.

Currently Papermerge 3 ~~2.2.x~~ is in active development.

The major feature for 3 ~~2.2.x~~ release, from user point of view, will be the support for OAuth2, OpenID Connect (OIDC) and LDAP authentications.

In general the whole authentication is being carved out into a separate microservice.
Sounds great, right? But what does it mean?

It means basically that authentication will not be performed by "papermerge-core" application, but in separate one. By default from 3 ~~2.2.x~~ onward the authentication will be performed by auth-server. As mentioned in first paragraph, auth-server will support oauth2, oidc and ldap in addition to default classical database user credentials authentication. The whole point of this feature, is that in case you want to replace default authentication system with another one e.g. authelia, keycloak etc you etc will be able to do so.

Why? You may wonder why would I need an external authenticator?

Well, because if you want to store your documents securely, then you may consider an 2FA authentication - and here were all external authentications come into the picture.
Or maybe you want to authenticate to your Papermerge instance with your github account (which has 2FA enabled of course)? This is where support of oauth2 protocol comes into the foreground.

Another change, which I guess is not relevant for end users, but still keeps me busy, is the replacement of emberjs based frontend with reactjs. Also in frontend I use now TypeScript instead of JavaScript. Frontend code base was moved into papermerge-core repository.

Yet another change, which I think is relevant, is that REST API will be now written in FastAPI instead of DRF; from end user perspective it means much cleaner (and complete, i.e. with detailed definition of all fields) documentation of REST API.

I will be posting development updates in this ticket.

Originally created by @ciur on GitHub (May 20, 2023). Original GitHub issue: https://github.com/ciur/papermerge/issues/548 Originally assigned to: @ciur on GitHub. Currently Papermerge 3 ~~2.2.x~~ is in active development. The major feature for 3 ~~2.2.x~~ release, from user point of view, will be the support for OAuth2, OpenID Connect (OIDC) and LDAP authentications. In general the whole authentication is being carved out into a separate microservice. Sounds great, right? But what does it mean? It means basically that authentication will not be performed by "papermerge-core" application, but in separate one. By default from 3 ~~2.2.x~~ onward the authentication will be performed by [auth-server](https://github.com/papermerge/auth-server). As mentioned in first paragraph, [auth-server](https://github.com/papermerge/auth-server) will support oauth2, oidc and ldap in addition to default classical database user credentials authentication. The whole point of this feature, is that in case you want to replace default authentication system with another one e.g. authelia, keycloak etc you etc will be able to do so. Why? You may wonder why would I need an external authenticator? Well, because if you want to store your documents securely, then you may consider an [2FA authentication](https://www.authelia.com/configuration/second-factor/introduction/) - and here were all external authentications come into the picture. Or maybe you want to authenticate to your Papermerge instance with your github account (which has 2FA enabled of course)? This is where support of oauth2 protocol comes into the foreground. Another change, which I guess is not relevant for end users, but still keeps me busy, is the replacement of emberjs based frontend with reactjs. Also in frontend I use now TypeScript instead of JavaScript. Frontend code base was moved into [papermerge-core](https://github.com/papermerge/papermerge-core/tree/master/ui) repository. Yet another change, which I think is relevant, is that REST API will be now written in FastAPI instead of DRF; from end user perspective it means much cleaner (and complete, i.e. with detailed definition of all fields) documentation of REST API. I will be posting development updates in this ticket.

kerem

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

closed this issue
added the
status

3.0
labels

kerem commented

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

Author

Owner

@ciur commented on GitHub (Sep 3, 2023):

A couple of points:

In order to avoid confusion, and be in line with semantic versioning - the release 2.2 will be re-titled 3.0. This is because 3.x won't be compatible with 2.x.
There is a new documentation page https://papermerge.github.io/documentation/; which is not yet official, but it will be in a month or so. In new docs it is more intuitive to switch between 2.0, 2.1 and 3.0. In new docs, version 3.0 is currently labeled 3.0-dev.

@ciur commented on GitHub (Sep 3, 2023): A couple of points: 1. In order to avoid confusion, and be in line with semantic versioning - the release 2.2 will be re-titled 3.0. This is because 3.x won't be compatible with 2.x. 2. There is a new documentation page https://papermerge.github.io/documentation/; which is not yet official, but it will be in a month or so. In new docs it is more intuitive to switch between 2.0, 2.1 and 3.0. In new docs, version 3.0 is currently labeled 3.0-dev.