September 2013 - Koha-devel - lists.koha-community.org

How to get CAS based Single Sign On working?
by Koustubha Kale 25 May '15

25 May '15

Hi All, I have a situation where we have a main website based on Joomla. This Joomla site uses CAS to authenticate users. We would like users ( who have already logged in to the Joomla site via CAS) to be able to follow a link to Koha site and be logged in automatically ( e.g. Single Sign On ). I have got simple CAS ( not proxy CAS ) working with Koha ( version 3.2.6 ) using the same CAS server as used by Joomla site. Still when I login to Joomla site with CAS, and then go to Koha and click on login and follow the CAS login link, I am asked to fill up CAS login information again. How can this be avoided by using CAS SSO? I have read through http://wiki.koha-community.org/wiki/SSO_CAS_improvements and am confused by the statement "Note: simple sso cas support (no proxy) has been done already by biblibre, is in testing and should be released in Koha 3.2" in there. Does this statement mean that SSO is possible with simple CAS? If yes how to set it up? If not, I have also read through bugs 6012, 5630 and the CAS Proxy examples. Frankly I haven't been able to figure out how I can achieve the above required functionality based on all the reading. Any help is much appreciated.. Another related query is, Is it possible to automatically create users in Koha once they have authenticated with CAS? Regards, Koustubha Kale Anant Corporation Contact Details : Address : 103, Armaan Residency, R. W Sawant Road, Nr. Golden Dyes Naka, Thane (w), Maharashtra, India, Pin : 400601. TeleFax : +91-22-21720108, +91-22-21720109 Mobile : +919820715876 Website : http://www.anantcorp.com Blog : http://www.anantcorp.com/blog/?author=2

3 3

koha-3.00.00 make fails
by Rick Welykochy 28 Dec '13

28 Dec '13

Hi all, I have downloaded http://download.koha.org/koha-3.00.00.tar.gz and began installing it on Debian/etch (in a Linux vserver environment). 0. FINE: cd koha-3.00.00 1. FINE: perl Makefile.PL 2. FAIL: make : : : Manifying blib/man3/C4::UploadedFile.3pm Manifying blib/man3/C4::BackgroundJob.3pm Manifying blib/man3/opac::opac-dictionary.3pm Manifying blib/man3/serials::member-search.3pm /usr/bin/perl "-Iblib/arch" "-Iblib/lib" fix-perl-path.PL blib /usr/bin/perl "-Iblib/arch" "-Iblib/lib" rewrite-config.PL blib/KOHA_CONF_DIR/koha-conf.xml Bad arg length for Socket::inet_ntoa, length is 0, should be 4 at rewrite-config.PL line 67. make: *** [blib/KOHA_CONF_DIR/koha-conf.xml] Error 255 Any ideas what went wrong and how to fix? Aside: there were a couple of other problems with this "out of the box" debian based install of Koha 3.0 which had to be fixed along the way, e.g. seven missing perl modules and libgd not found. I'll report on the entire process from unpacking to a running Koha/3.00.00 once I get to the end. cheers rickw -- ________________________________________________________________ Rick Welykochy || Praxis Services || Internet Driving Instructor The manual said Windows XP/SP2 or better so I installed Linux.

4 5

Koha 3.12.x and VIAF
by Partha Mukhopadhyay 29 Nov '13

29 Nov '13

2 1

New newsletter editor volunteer
by Daniel Grobani 05 Nov '13

05 Nov '13

Hi, Chad Roseburg of North Central Regional Library has volunteered to assume the role of community newsletter editor starting with the December issue. Thanks, Chad! As I recall, when I took over from Nicole the only requirement was the willingness to do it. What's the current process for Chad to get approved by the community? Thanks, Daniel Grobani

3 3

Linking bibs to authorities
by Ian Bays 24 Oct '13

24 Oct '13

Hi. I mentioned we also have a problem with linking bibs to authorities. We use authorities and want to link them to bibs. Over previous versions of Koha this has sometimes worked quite well. However on a few systems we have at version 3.12 it seems that the Zebra search into the authorities (used by link_bib_to_authorities) is returning all terms that contain any of the words in the bib field. So if the linkage is set to "default" then most authority searches will return multiple answers which means they do not link. If the linkage syspref is set to first or last then most of the bibs will link to the wrong authority as it is pot luck which will be first (or last) of the many authorities found by searching all the words ORed together. The only terms that will link are single-word authorities that are not used in any other authorities. If anyone has any pointers or knows how to get round or over this problem I would love to hear from you. More details on request... We are using Zebra dom indexing and icu chains and are using Koha 3.12 on Debian. We are not yet using QueryParser. Sysprefs and Help > About are here: Sysprefs are: +--------------------------+-------+ | variable | value | +--------------------------+-------+ | IncludeSeeFromInSearches | 0 | | QueryAutoTruncate | 0 | | QueryFuzzy | 0 | | QueryStemming | 0 | | QueryWeightFields | 1 | | TraceCompleteSubfields | 0 | | TraceSubjectSubdivisions | 0 | | UseICU | 1 | | UseQueryParser | 0 | +--------------------------+-------+ Koha> About: Koha version: 3.12.01.000 OS version ('uname -a'): Linux dclg.koha.ptfsadmin.uk0.bigv.io 3.2.0-4-amd64 #1 SMP Debian 3.2.46-1 x86_64 GNU/Linux Perl interpreter: /usr/bin/perl Perl version: 5.014002 Perl @INC: /home/koha/kohaclone /etc/perl /usr/local/lib/perl/5.14.2 /usr/local/share/perl/5.14.2 /usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.14 /usr/share/perl/5.14 /usr/local/lib/site_perl . MySQL version: mysql Ver 14.14 Distrib 5.5.31, for debian-linux-gnu (x86_64) using readline 6.2 Apache version: Server version: Apache/2.2.22 (Debian) Zebra version: Zebra 2.0.55 (C) 1994-2013, Index Data ApS Zebra is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. SHA1 ID: bd2bc9360225e695bbaba2c2d1cd6925c4eb23a5 Using ICU Many thanks folks. Ian -- Ian Bays Director of Projects, PTFS Europe Limited Content Management and Library Solutions +44 (0) 800 756 6803 (phone) +44 (0) 7774 995297 (mobile) +44 (0) 800 756 6384 (fax) skype: ian.bays email: ian.bays(a)ptfs-europe.com

6 10

General questions from a first-patcher
by Philippe Blouin 03 Oct '13

03 Oct '13

Holà Koha! First to present myself, I'm a new developper on Koha. I work for inLibro, which has been a Koha proponent for a while now. All our changes, enhancements and bug fixes have been local so far, meaning we patched for each library as they needed. We got a bundle of those to contribute to the community. Fixes and enhancements. To get the hang of it, I started with three small ones (after dutifully reading the wiki, blog and asking irc questions), but I'm sure I screwed up a few things. I will appreciate _any_ and _every_ constructive comments you can make on the following: http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6201 http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8753 http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10951 Questions: - I work with patches. I used git-bz for one, and manual for the others. Now how to I email to patch mailing list? I just copy the content? I comment it? Do I add the [PATCH] in the header or some tool could have done all that for me? (my server can't send email, so I'm not sure if git-bz should have done it) - My local branch names are bug_XXXX from the master. But I'm not sure if that must be commited. Some wiki (contribute!) only talks about sending a patch. Others (http://wiki.koha-community.org/wiki/Commit_messages) talk about it. Can you enlighten me? Long text for two questions. Sorry. But I need that clarified before I start piling up fixes :) Very best regards, Blou -- Philippe Blouin, Responsable du développement informatique Tél. : (888) 604-2627 philippe.blouin(a)inLibro.com <mailto:philippe.blouin@inLibro.com> inLibro | pour esprit libre | www.inLibro.com <http://www.inLibro.com>

5 13

Bug (or something) repeatedly loading the same URL over and over.
by Robin Sheat 03 Oct '13

03 Oct '13

I just saw a thing that I've seen a few times before, and have heard anecdotally that others have too. The problem is that something hits the same URL over and over, eventually knocking over the server. I have some theories, but they're hard to test because this is a rare thing to happen, so I want to see if anyone else has seen something like this. It seems like some kind of search complete or similar running, however CircAutocompl is off. This is a 3.6 machine, though I think I've also seen it on 3.8. Haven't had anything higher running in prod long enough to tell. The log is below. I've reordered it to be when the request is issued rather than when it finishes to make it clearer, and added my speculation in. This is a real request by a human to view details. 172.20.2.200 - - [27/Sep/2013:13:29:01 +1200] "GET /cgi-bin/koha/members/moremember.pl?borrowernumber=16653 HTTP/1.1" 200 7202 This is some kind of automatic process that autocompletes, or something, that's going out of control. There's more of them, but you get the drift: 172.20.2.200 - - [27/Sep/2013:13:29:06 +1200] "POST /cgi-bin/koha/members/member.pl HTTP/1.1" 504 270 172.20.2.200 - - [27/Sep/2013:13:29:07 +1200] "POST /cgi-bin/koha/members/member.pl HTTP/1.1" 504 270 172.20.2.200 - - [27/Sep/2013:13:29:07 +1200] "POST /cgi-bin/koha/members/member.pl HTTP/1.1" 504 270 172.20.2.200 - - [27/Sep/2013:13:29:07 +1200] "POST /cgi-bin/koha/members/member.pl HTTP/1.1" 504 270 172.20.2.200 - - [27/Sep/2013:13:29:07 +1200] "POST /cgi-bin/koha/members/member.pl HTTP/1.1" 504 270 172.20.2.200 - - [27/Sep/2013:13:29:07 +1200] "POST /cgi-bin/koha/members/member.pl HTTP/1.1" 504 270 172.20.2.200 - - [27/Sep/2013:13:29:09 +1200] "POST /cgi-bin/koha/members/member.pl HTTP/1.1" 504 270 172.20.2.200 - - [27/Sep/2013:13:29:07 +1200] "POST /cgi-bin/koha/members/member.pl HTTP/1.1" 504 270 172.20.2.200 - - [27/Sep/2013:13:29:07 +1200] "POST /cgi-bin/koha/members/member.pl HTTP/1.1" 504 270 172.20.2.200 - - [27/Sep/2013:13:29:09 +1200] "POST /cgi-bin/koha/members/member.pl HTTP/1.1" 504 270 I don't know what this is or what it's doing here: 172.20.2.200 - - [27/Sep/2013:13:29:11 +1200] "GET /cgi-bin/koha/circ/circulation.pl?borrowernumber=16653 HTTP/1.1" 504 270 172.20.2.200 - - [27/Sep/2013:13:29:18 +1200] "GET /cgi-bin/koha/circ/circulation.pl?borrowernumber=16653 HTTP/1.1" 504 270 172.20.2.200 - - [27/Sep/2013:13:29:10 +1200] "GET /cgi-bin/koha/circ/circulation.pl?borrowernumber=16653 HTTP/1.1" 504 270 172.20.2.200 - - [27/Sep/2013:13:29:12 +1200] "GET /cgi-bin/koha/circ/circulation.pl?borrowernumber=16653 HTTP/1.1" 504 270 172.20.2.200 - - [27/Sep/2013:13:29:10 +1200] "GET /cgi-bin/koha/circ/circulation.pl?borrowernumber=16653 HTTP/1.1" 504 270 172.20.2.200 - - [27/Sep/2013:13:29:13 +1200] "GET /cgi-bin/koha/circ/circulation.pl?borrowernumber=16653 HTTP/1.1" 504 270 172.20.2.200 - - [27/Sep/2013:13:29:11 +1200] "GET /cgi-bin/koha/circ/circulation.pl?borrowernumber=16653 HTTP/1.1" 504 270 172.20.2.200 - - [27/Sep/2013:13:29:11 +1200] "GET /cgi-bin/koha/circ/circulation.pl?borrowernumber=16653 HTTP/1.1" 504 270 172.20.2.200 - - [27/Sep/2013:13:29:12 +1200] "GET /cgi-bin/koha/circ/circulation.pl?borrowernumber=16653 HTTP/1.1" 504 270 172.20.2.200 - - [27/Sep/2013:13:29:13 +1200] "GET /cgi-bin/koha/circ/circulation.pl?borrowernumber=16653 HTTP/1.1" 504 270 172.20.2.200 - - [27/Sep/2013:13:29:12 +1200] "GET /cgi-bin/koha/circ/circulation.pl?borrowernumber=16653 HTTP/1.1" 504 270 172.20.2.200 - - [27/Sep/2013:13:29:17 +1200] "GET /cgi-bin/koha/circ/circulation.pl?borrowernumber=16653 HTTP/1.1" 504 270 172.20.2.200 - - [27/Sep/2013:13:29:16 +1200] "GET /cgi-bin/koha/circ/circulation.pl?borrowernumber=16653 HTTP/1.1" 504 270 It just keeps going like this until I stop apache, and when I start it up again, this doesn't immediately recur. My theory is that there's some javascript somewhere that just loses it and goes mad, but I don't know. Any ideas? This only comes up once every few months, but when it does, it can take the server down. -- Robin Sheat Catalyst IT Ltd. ✆ +64 4 803 2204 GPG: 5FA7 4B49 1E4D CAA4 4C38 8505 77F5 B724 F871 3BDF

4 7

September 2013 Koha Community Newsletter has been published
by Daniel Grobani 30 Sep '13

30 Sep '13

Hi, The September 2013 edition of the Koha Community Newsletter has been posted to http://koha-community.org/koha-community-newsletter-september-2013/. Cheers, Daniel Grobani Koha Community Newsletter Editor

1 0

Module MARC::Record doesn't set well lenght in leader.
by Zeno Tajoli 30 Sep '13

30 Sep '13

Hi to all, [sorry the previous mail is incomplete] I have a problem with creating marc21 records with module MARC::Record I create marc records from reading a text file, but the module doesn't set a correct lenght in the leader. So same subfields are cutted and I loose data inside subfiels and inside indicator. An example of problematic record: DB<10> x $record 0 MARC::Record=HASH(0x53904f8) '_fields' => ARRAY(0x5471fa8) 0 MARC::Field=HASH(0x54694b8) '_data' => 328 '_is_control_field' => 1 '_tag' => 001 '_warnings' => ARRAY(0x53bb8d8) empty array 1 MARC::Field=HASH(0x545ea10) '_data' => 'IT-RoAPU' '_is_control_field' => 1 '_tag' => 003 '_warnings' => ARRAY(0x545df00) empty array 2 MARC::Field=HASH(0x5460d78) '_data' => 20130929162908.0 '_is_control_field' => 1 '_tag' => 005 '_warnings' => ARRAY(0x592ee28) empty array [...] 15 MARC::Field=HASH(0x546b1a8) '_ind1' => 0 '_ind2' => 0 '_is_control_field' => 0 '_subfields' => ARRAY(0x541c940) 0 'a' 1 'Biblia.' 2 'p' 3 'V.T.' 4 'p' 5 'Qohélet' 6 'x' 7 'Commenti.' 8 9 9 171552 '_tag' => 630 '_warnings' => ARRAY(0x5465538) empty array 16 MARC::Field=HASH(0x5465a18) '_ind1' => ' ' '_ind2' => ' ' '_is_control_field' => 0 '_subfields' => ARRAY(0x5466cd0) 0 'a' 1 'Biblia.' 2 'p' 3 'V.T.' 4 'p' 5 'Qohélet.' 6 'l' 7 'Inglese.' 8 'f' 9 1988. 10 9 11 17155 '_tag' => 240 '_warnings' => ARRAY(0x5477168) empty array 17 MARC::Field=HASH(0x5462fa8) '_ind1' => ' ' '_ind2' => ' ' '_is_control_field' => 0 '_subfields' => ARRAY(0x541eb38) 0 'a' 1 'IT-RoAP' '_tag' => 850 '_warnings' => ARRAY(0x5931948) empty array 18 MARC::Field=HASH(0x5469788) '_ind1' => ' ' '_ind2' => ' ' '_is_control_field' => 0 '_subfields' => ARRAY(0x5472170) 0 'c' 1 32 '_tag' => 999 '_warnings' => ARRAY(0x54693f8) empty array '_leader' => '00859nam a2200265 i 4500' '_warnings' => ARRAY(0x53682b0) 0 'Invalid record length in record 324: Leader says 00859 bytes but it\'s actually 861' 1 'field does not end in end of field character in tag 630 in record 324' 2 'field does not end in end of field character in tag 240 in record 324' 3 "Invalid indicators \"\c^02\" forced to blanks in record 324 for tag 240\cJ" 4 'field does not end in end of field character in tag 850 in record 324' 5 "Invalid indicators \"3\c^ \" forced to blanks in record 324 for tag 850\cJ" 6 'field does not end in end of field character in tag 999 in record 324' 7 "Invalid indicators \"U\c^ \" forced to blanks in record 324 for tag 999\cJ" In fact indicator of tag 240 are wrong (the correct values are '02'); the real value of 240 $9 is '171553', not '17155'. The real value of 850 $a is 'IT-RoAPU', not 'IT-RoAP' The real value of 999 $c is '328', not '32' As I see the problem start for word 'Qohélet' in the tag 240 and 630. I don't know why the leght is wrong and I don't have idea how to fix it. Chees Zeno Tajoli -- Dr. Zeno Tajoli Dipartimento Gestione delle Informazioni e della Conoscenza z.tajoli(a)cineca.it fax +39 02 2135520 CINECA - Sede operativa di Segrate

4 5

Critical LDAP issue in 3.12/master
by Robin Sheat 30 Sep '13

30 Sep '13

There's a nasty bug in 3.12 that will break LDAP connections in some configurations, particularly when talking to active directory. There is a fix at http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10908 however it needs signoff. So if you're using LDAP, auth_by_bind, and don't have an anonymous user with access to search your user database (which I get the impression is a fairly standard scenario), please have a look at this and sign it off, as I'd like to get it into a release Real Soon Now. Thanks! (PS, unrelated, I'm using a new GPG key. So if you use that, you should probably fetch this one: F8713BDF.) -- Robin Sheat Catalyst IT Ltd. ✆ +64 4 803 2204 GPG: 5FA7 4B49 1E4D CAA4 4C38 8505 77F5 B724 F871 3BDF

1 0