Quote:
Originally Posted by kovidgoyal
Sigh, I am going to try this one last time, just because I am eternal optimist.
1) You sync user accounts from LDAP to calibre with default passwords. i.e. the same dummy password for all user accounts.
2) You get Apache to re-write the Authorization header so it contains the username and this default password instead of the actual password.
|
Then we came to a similar solution, as I wrote, this is almost what I do now. Me too rewrite the AuthHeaders in Apache, not just the Password but the users to default ones too. This would be easier, cause in the other case one had to base64-encode the dynamic usernames with the help of the apache config (The AuthString for BasicAuth is bas64 encoded form of "username: password"); don't figured out if and how this is possible. This is my solution:
Code:
#NonAdult
RequestHeader set Authorization "Basic <NonAdultUserPassString>" expr=(%{REMOTE_USER}in{"Sarah"})
#All
RequestHeader set Authorization "Basic <AllUserPassString>" expr=(%{REMOTE_USER}in{"John","Jane"})
This means I have just one technical user with an unimportant password for each virt lib and just "map" the LDAP Users to these technical calibre users.
This complicates things a little compaired to V2 but it generally woks.
Quote:
Originally Posted by kovidgoyal
4) You cannot run the server and the GUI at the same time because they both can make changes to the calibre library. Pick one.
|
I know, I don't do this even in V2. I have one little "Work" library where I import new Books edit them to my needs with the calibre Windows GUI and then - also with the calibre GUI - move the finished Book to the "Online" library which calibre-server on the linnux-vm serves. Works quite good.
Quote:
Originally Posted by kovidgoyal
I am done with this thread. It seems to be filled with people asking the same questions over and over again, despite my having them answered already.
|
Why so excited? Just relax, and perhaps think a little, WHY many people ask similar questions, there must be a reason for it...
We just all want to help make this good software even better.. a single developer can't think of (and less test) each and every use case that could came up in a larger community like this one of calibre, just quite normal. So shouldn't you be a little more thankful of the communities contribution?