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

[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 02 Jan '15

02 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 1861] Unique patrons logins not (totally) enforced
by bugzilla-daemon＠bugs.koha-community.org 01 Jan '15

01 Jan '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=1861 Tomás Cohen Arazi <tomascohen(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Pushed by Module Maintainer |Pushed to Master --- Comment #33 from Tomás Cohen Arazi <tomascohen(a)gmail.com> --- Followups pushed to master. Thanks Chris and Jonathan! -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 1861] Unique patrons logins not (totally) enforced
by bugzilla-daemon＠bugs.koha-community.org 31 Dec '14

31 Dec '14

1 0

[Bug 1861] Unique patrons logins not (totally) enforced
by bugzilla-daemon＠bugs.koha-community.org 31 Dec '14

31 Dec '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=1861 Tomás Cohen Arazi <tomascohen(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #33984|[PASSED QA] Bug 1861 [QA |[PUSHED] Bug 1861 [QA description|Followup] - Fix |Followup] - Fix |Check_Userid and unit tests |Check_Userid and unit tests -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 1861] Unique patrons logins not (totally) enforced
by bugzilla-daemon＠bugs.koha-community.org 31 Dec '14

31 Dec '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=1861 Tomás Cohen Arazi <tomascohen(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #33983|[PASSED QA] Bug 1861 - |[PUSHED] Bug 1861 - Unique description|Unique patrons logins not |patrons logins not |(totally) enforced |(totally) enforced -- You are receiving this mail because: You are watching all bug changes.

1 0

[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 3511] Integration with Moodle
by bugzilla-daemon＠bugs.koha-community.org 31 Dec '14

31 Dec '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=3511 Martin Renvoize <martin.renvoize(a)ptfs-europe.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED CC| |martin.renvoize@ptfs-europe | |.com Resolution|--- |INVALID --- Comment #2 from Martin Renvoize <martin.renvoize(a)ptfs-europe.com> --- As suggested above, I believe on the authetncation front that we can interoperate nicely with Moodle now (With, both CAS and Shibboleth support). If we want more in depth Moodle integration, then I believe that should be opened as it's own bug with a clear definition of what people are wanting/aiming to achieve. Marking this bug RESOLVED INVALID -- You are receiving this mail because: You are the QA Contact for the bug. You are watching all bug changes.

1 0