| Summary: | Error 403 when login OPAC and Intranet | ||
|---|---|---|---|
| Product: | Koha | Reporter: | Claudio Costales <costalc> |
| Component: | Authentication | Assignee: | Bugs List <koha-bugs> |
| Status: | REOPENED --- | QA Contact: | Testopia <testopia> |
| Severity: | critical | ||
| Priority: | P1 - high | CC: | costalc, dpavlin, schodkowy.omegi-0r, taylor.emric.ae |
| Version: | 24.11 | ||
| Hardware: | All | ||
| OS: | All | ||
| GIT URL: | Initiative type: | --- | |
| Sponsorship status: | --- | Comma delimited list of Sponsors: | |
| Crowdfunding goal: | 0 | Patch complexity: | --- |
| Documentation contact: | Documentation submission: | ||
| Text to go in the release notes: | Version(s) released in: | ||
| Circulation function: | |||
|
Description
Claudio Costales
2025-03-02 02:12:20 UTC
After upgrading from 24.05 to 24.11 sudo apt upgrade message: ********************** 1 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] Setting up koha-common (24.11.02-1) ... Upgrading database schema XXXX dpkg: error processing package koha-common (--configure): installed koha-common package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: koha-common E: Sub-process /usr/bin/dpkg returned an error code (1) ****************************** "sudo koha-translate --update $lang" and all went fine. I admit I had similar issue with `E: Sub-process /usr/bin/dpkg returned an error code (1)` on koha-staging repo branch. There's possibly some bug there, it's not supposed to happen, not sure if it should be marked as RESOLVED yet... I think so too. It's an attention point to be considered. Reopened. Third party auth is not working. Includes CASSIE, Libby, OverDrive, and self-checkout stations. Update from 24.04 to 24.11. (In reply to taylor.emric.ae from comment #6) > Third party auth is not working. Includes CASSIE, Libby, OverDrive, and > self-checkout stations. Update from 24.04 to 24.11. Hi there :) I believe your issue is a separate bug or configuration issue. Are you self hosted or do you have a support commpany you could contact? For community support, please try the mailing list or community chat. Important information to include is how you are authenticating with those vendors. I guess it might be SIP2, as you say it also affects your self check stations. |