Skip to content

Cannot add HTTPS OPDS catalog #1368

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
hydrian opened this issue Mar 10, 2025 · 2 comments · May be fixed by #1378
Open

Cannot add HTTPS OPDS catalog #1368

hydrian opened this issue Mar 10, 2025 · 2 comments · May be fixed by #1378

Comments

@hydrian
Copy link

hydrian commented Mar 10, 2025

When I try to add my opds catalogue, it get the follow error:

Invalid value OPDS https://ebooks.tygerclan.lan/opds

If I browse to that url in a browser, I get asked of HTTP basic authentication credentials. Once provided valid credentials, it shows the OPDS xml.

I then configured CWA's service to accept HTTP connects. Librera connected fine.

Not having HTTPS is not a long term solution because the user passwords are reused all over the network because of LDAP.

I'm selfhosting a calibre-web-automated(aka CWA) service. CWA is configured to use LDAP for authentication and HTTPS. The Root CA for the for issued HTTPS device is fully supported by my Android device and works properly with other applications.

@hydrian
Copy link
Author

hydrian commented Mar 10, 2025

I looked at the code a bit and noticed that the android manifest does not support user root CA certificate stores. This is important for many selfhosters.

I can't remember if it was Android 7 or 11 that Android apps had to explicitly allowed user CA certificates (via the device config ) in the manifest. Previously, Android apps would use both the system and user root CA device certificate stores.

I made the manifest changes here: https://github.com/hydrian/LibreraReader/tree/ssl
Once I get a good build and test, I'll do a PR.

@hydrian
Copy link
Author

hydrian commented Mar 22, 2025

I deployed a certificate with a public CA root and Librera worked fine. So, this definitely looks like Librera doesn't support user installed root CAs.

To resolve this, it is just an update to the android manifest. I'll be providing a PR to resolve this.

@hydrian hydrian linked a pull request Mar 22, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant