@kovid
Because of your very common statement which can just be found in the calibre docs, I think you didn't really read / understood my post, do you?
It's absolutly clear that one calibre-server can serve multiple virtual libraries with the help of the new userdb in a very simple use case. I absolutly understood how this works as I implemented that for testing without the apache proxy, no problem.
But with the current restriction (no multiple calibre-server instances allowed) my use case I described above is much harder / impossible(?) to implement.
Please answer this core question resulting of my scenario and the restrictions you implemented with V3:
How can a single (existing)
apache with enabled Basic Auth and LDAP Backend as own User / Group Management act as a single-entry-point ReverseProxy for multiple virtual libraries if just one calibre server with one url-prefix and one port may run?
It is NOT possible to have multiple Basic Auths (first the one from apache and second the one from calibre afterwards) one after the other.
To explain this further:
You open the URL of the apache reverseproxy for one calibre-server lets say:
https://myhost.dyndns.org/calibre
(calibre-server in the backend runs with "--url-prefix /calibre" and enabled auth with a userdb)
Now this happens:
- The BasicAuth of Apache kicks in and you have to enter valid credentials of a LDAP User
- Directly afterwards the calibre BasicAuth wants to have valid credentials of a calibre user (mapping a virtual library)
- Every following request (XHR, whatever...) fails with a "401 Unauthorized" by calibre, because the browser always sends the FIRST BasicAuth credentials (from the Apache)
Just try urself... So I ask u again: How would u solve this problem with V3?
(BTW: In general it would be not very comfortable to have to enter different credentials twice for entering a service even it would technically work...)