October 2014 - Koha-bugs - lists.koha-community.org

[Bug 6349] New: auto print hold slip
by bugzilla-daemon＠bugs.koha-community.org 02 Jan '15

02 Jan '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6349 Bug #: 6349 Summary: auto print hold slip Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Hold requests AssignedTo: ian.walls(a)bywatersolutions.com ReportedBy: nengard(a)gmail.com QAContact: koha-bugs(a)lists.koha-community.org CC: gmcharlt(a)gmail.com It would be nice if when you checked a book in that was on hold a hold slip was printed automatically. -- Configure bugmail: http://bugs.koha-community.org/bugzilla3/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA Contact for the bug.

1 2

[Bug 7754] New: displaying the number of days a document is late
by bugzilla-daemon＠bugs.koha-community.org 02 Jan '15

02 Jan '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7754 Priority: P5 - low Change sponsored?: --- Bug ID: 7754 CC: gmcharlt(a)gmail.com Assignee: kyle.m.hall(a)gmail.com Summary: displaying the number of days a document is late QA Contact: koha.sekjal(a)gmail.com Severity: enhancement Classification: Unclassified OS: All Reporter: gaetan.boisson(a)biblibre.com Hardware: All Status: NEW Version: master Component: Circulation Product: Koha On the return screen, when a document is late, the return date column give the date the document should have been returned, in red. Displaying the number of days the document is late next to it would be useful. -- You are receiving this mail because: You are watching all bug changes.

1 6

[Bug 12774] New: Enabling phone notices ( talking tech ) without having DUEDGST and PREDUEDGST breaks advance notices!
by bugzilla-daemon＠bugs.koha-community.org 02 Jan '15

02 Jan '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12774 Bug ID: 12774 Summary: Enabling phone notices ( talking tech ) without having DUEDGST and PREDUEDGST breaks advance notices! Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: critical Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 7

[Bug 5441] New: SSO CAS improvements
by bugzilla-daemon＠bugs.koha-community.org 02 Jan '15

02 Jan '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5441 Summary: SSO CAS improvements Change sponsored?: Sponsored Product: Koha Version: rel_3_4 Platform: All URL: http://wiki.koha-community.org/wiki/SSO_CAS_improvemen ts OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Authentication AssignedTo: henridamien(a)koha-fr.org ReportedBy: paul.poulain(a)biblibre.com QAContact: koha-bugs(a)lists.koha-community.org CC: dpavlin(a)rot13.org Estimated Hours: 0.0 Multitier proxy authentication support with CAS 2.0 for SSO. See http://www.jasig.org/cas in general and http://www.ja-sig.org/wiki/display/CAS/Proxy+CAS+Walkthrough specifically. Koha should be able to accept a proxy ticket, i.e. authenticate with CAS without being directly in contact with the client's browser, e.g. in the case of patron information being requested through a web service by a portal from koha. Note: simple sso cas support (no proxy) has been done already by biblibre, is in testing and should be released in Koha 3.2 -- Configure bugmail: http://bugs.koha-community.org/bugzilla3/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.

1 4

[Bug 12547] New: Create better API for handling external authentication
by bugzilla-daemon＠bugs.koha-community.org 01 Jan '15

01 Jan '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12547 Bug ID: 12547 Summary: Create better API for handling external authentication Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Authentication Assignee: gmcharlt(a)gmail.com Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org CC: dpavlin(a)rot13.org At the moment, authentication is really handled all that consistently. There is Auth_with_cas.pm, Auth_with_ldap.pm, and perhaps one day Auth_with_Shibboleth.pm. There is also Persona which relies on a DOM API and Javascript on some OPAC pages. All of these different methods also hook into Auth.pm. They all work but it's not really that easy to see how they work nor is it straightforward to add new forms of external authentication. I don't have a plan of how to improve C4::Auth::checkauth() or C4::Auth, but I think it's worth thinking about. Obviously, it would require a ton of testing, but perhaps we could have incremental improvements. -- You are receiving this mail because: You are watching all bug changes.

1 7

[Bug 12227] New: remove demo user functionality
by bugzilla-daemon＠bugs.koha-community.org 31 Dec '14

31 Dec '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12227 Bug ID: 12227 Summary: remove demo user functionality Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Authentication Assignee: gmcharlt(a)gmail.com Reporter: gmcharlt(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: dpavlin(a)rot13.org There is a legacy authentication mode whereby if you enable a "demo" setting in koha-conf.xml, one can log in as a user with username "demo" and password "demo". This user acts as a superlibrarian with two exceptions: [1] not able to modify system preferences [2] not able to save changes to MARC frameworks This represents a wart in the authentication code for a very limited use case -- and warts in authentication code can turn into security exposures. The special case should be removed. If folks still want to be able to create demo systems with high-privilege staff accounts that can't touch MARC frameworks or system preferences, that can be addressed by adding a couple more granular permissions. -- You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 8865] New: Re-logging in needs to pass POST & GET arguments
by bugzilla-daemon＠bugs.koha-community.org 30 Dec '14

30 Dec '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8865 Priority: P5 - low Change sponsored?: --- Bug ID: 8865 CC: dpavlin(a)rot13.org Assignee: gmcharlt(a)gmail.com Summary: Re-logging in needs to pass POST & GET arguments Severity: minor Classification: Unclassified OS: All Reporter: kyle(a)bywatersolutions.com Hardware: All Status: NEW Version: master Component: Authentication Product: Koha When a librarian is forced to re-login for an action ( either for super-librarian privileges, or because of a timeout ), this should pass in both GET and POST arguments to the page that we forward to. Not doing so causes problems, a case in point is bug 8860's error message. -- You are receiving this mail because: You are watching all bug changes.

1 1

[Bug 8785] New: Basic authentication troubleshootings
by bugzilla-daemon＠bugs.koha-community.org 30 Dec '14

30 Dec '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8785 Priority: P5 - low Change sponsored?: --- Bug ID: 8785 CC: dpavlin(a)rot13.org Assignee: gmcharlt(a)gmail.com Summary: Basic authentication troubleshootings Severity: normal Classification: Unclassified OS: All Reporter: matthias.meusburger(a)biblibre.com Hardware: All Status: NEW Version: master Component: Authentication Product: Koha I've ran several tests with basic http authentication in koha, and here's what I found: When using basic http authentication at OPAC, if the loggedin username does not match a valid koha user, that leads to a session with borrowernumber 0. When using basic http authentication at Intranet, if the loggedin username does not match a valid koha user, that also leads to a session with borrowernumber 0. At the top-right of the screen, I can see "insecure" in bold black. However, my "insecure" syspref is set to 0. Is this behavior normal? Steps to reproduce: To use basic http authentication at OPAC, create a .htaccess and a .htpasswd file in the 'opac' directory. To use basic http authentication at Intranet, create a .htaccess and a .htpasswd file at the root of the source directory (don't forget to backup the existing .htaccess) In order to easily generate .htaccess and .htpasswd, you can use the following tools: http://www.htaccesstools.com/htaccess-authentication/ http://www.htaccesstools.com/htpasswd-generator/ -- You are receiving this mail because: You are watching all bug changes.

1 1

[Bug 6804] New: If IndependantBranches and AutoLocation enabled, OPAC login does not redirect properly outside IP range
by bugzilla-daemon＠bugs.koha-community.org 30 Dec '14

30 Dec '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6804 Bug #: 6804 Summary: If IndependantBranches and AutoLocation enabled, OPAC login does not redirect properly outside IP range Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_6 Platform: All OS/Version: All Status: ASSIGNED Severity: minor Priority: P5 Component: Authentication AssignedTo: ian.walls(a)bywatersolutions.com ReportedBy: ian.walls(a)bywatersolutions.com QAContact: koha-bugs(a)lists.koha-community.org CC: dpavlin(a)rot13.org In the event that a library has IndependantBranches turned on, as well as AutoLocation turned on and valid IP ranges in place for their branches, the OPAC login will not redirect to the My Summary area; it will instead show another login prompt. The login is indeed successful, and if the patron navigates to other pages, they will find the link to their account in the upper right corner as normal, but this initial prompt is VERY discouraging. -- Configure bugmail: http://bugs.koha-community.org/bugzilla3/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA Contact for the bug.

1 10

[Bug 12596] New: Backdating returns with SpecifiyReturnDate causes fines for items not overdue!
by bugzilla-daemon＠bugs.koha-community.org 29 Dec '14

29 Dec '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12596 Bug ID: 12596 Summary: Backdating returns with SpecifiyReturnDate causes fines for items not overdue! Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: critical Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When using the backdating of returns feature, an item that is not overdue is treated as being as many days overdue as it is *not* overdue. This is due to the fact that _get_chargeable_units appears to return the difference between the return date and the due date without consideration the return date being earlier than the due date. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 18