Re: [Koha] SSO Shibboleth & oauth issues
Really appreciate this. Both the Shibboleth and OAuth issues are happening for fresh logins, or how you've tested after a Koha logout. I've reproduced it consistently in an incognito window, which simulates fresh and isolated cookie and session data but clearing once the window is closed, not an anonymous session persay, or is this what an anonymous session actually is? Most of our users would be logging in afresh without an existing session. This replicating the users first experience after attempting a login to Koha. Justin Dowswell (he/him) Technology Coordinator Tenants' Union of NSW 02 8117 3721 On Fri, 30 Jun 2023 at 12:09, David Cook wrote: > Hey Justin, > > > > I’ve raised a ticket for this: > https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34163 > > > > I was only able to reproduce the problem after a Koha logout. When are you > experiencing this problem with OAuth? > > > > The issue appears to stem from the handling of anonymous user sessions and > logging out. But curious if you’re experiencing it in other contexts… > > > > David Cook > > Senior Software Engineer > > Prosentient Systems > > Suite 7.03 > > 6a Glen St > > Milsons Point NSW 2061 > > Australia > > > > Office: 02 9212 0899 > > Online: 02 8005 0595 > > > > *From:* David Cook > *Sent:* Friday, 30 June 2023 11:22 AM > *To:* 'Justin Dowswell' > *Cc:* 'koha@lists.katipo.co.nz' > *Subject:* RE: [Koha] SSO Shibboleth & oauth issues > > > > We’re everywhere! > > > > Well, the good news is that I’ve reproduced your error when testing OIDC > on the master code branch. > > > > But the bad news is that I’ve reproduced your error when testing OIDC on > the master code branch. > > > > I haven’t tested the Shibboleth integration yet as it’s more work to set > up, but it could be related. > > > > The OIDC is working fine in 22.11.03, so it looks like it was broken > between 22.11 and 23.05. > > > > I’ll look at fixing this one. (Authentication is a special interest of > mine, so I’m usually a good person to ask about these things.) > > > > But if you can check the Koha logs for anything obvious for your > Shibboleth issue in the meantime – that would be helpful. > > > > David Cook > > Senior Software Engineer > > Prosentient Systems > > Suite 7.03 > > 6a Glen St > > Milsons Point NSW 2061 > > Australia > > > > Office: 02 9212 0899 > > Online: 02 8005 0595 > > > > *From:* Justin Dowswell > *Sent:* Friday, 30 June 2023 11:02 AM > *To:* David Cook > *Cc:* koha@lists.katipo.co.nz > *Subject:* Re: [Koha] SSO Shibboleth & oauth issues > > > > Hey David, > > > > It's good to know there is a Koha community active so close to us! > > > Great. > > > > So we're running 23.05 on Debian Bullseye installed using apt. > > > > I'll have a look through Koha's logs. We're using OAuth as an alternative, > using the same IdP. > > > > Justin Dowswell > > Technology Coordinator > > Tenants' Union of NSW > > 02 8117 3721 > > > > > > On Fri, 30 Jun 2023 at 09:46, David Cook wrote: > > Hey Justin, > > Sorry to hear you're having issues, but great to see another organisation > in NSW using Koha! > > Let's see if we can help you sort out this issue. What version of Koha are > you running, how did you install it, and on which Linux distro? > > With the Shibboleth, you'll want to look at your Koha logs. With the other > auth, are you using OAuth or OIDC? > > David Cook > Senior Software Engineer > Prosentient Systems > Suite 7.03 > 6a Glen St > Milsons Point NSW 2061 > Australia > > Office: 02 9212 0899 > Online: 02 8005 0595 > > -Original Message- > > Date: Wed, 28 Jun 2023 23:49:06 +1000 > From: Justin Dowswell > To: koha@lists.katipo.co.nz > Subject: [Koha] SSO Shibboleth & oauth issues > Message-ID: > < > cagzh+upebxvz2asoxmyyxhbctmy3mylh3ubpfvyqyzcrcqh...@mail.gmail.com> > Content-Type: text/plain; charset="UTF-8" > > Hey everyone, > > I am Justin from the Tenants’ Union of NSW. Lovely to meet you all, albeit > in an archaic manner. > > There is a Koha issue I am having trouble resolving… > > It’s a strange issue with Shibboleth and now I think the same issue > displayed differently with oauth (that I wanted to implement as an > alternative), both using the same IdP, and definitely isolated to Koha > and/or the server running it. I believe it’s a caching issue of some sort… > > When I get redirected back to Koha after a successful lo
Re: [Koha] SSO Shibboleth & oauth issues
Hey David, It's good to know there is a Koha community active so close to us! Great. So we're running 23.05 on Debian Bullseye installed using apt. I'll have a look through Koha's logs. We're using OAuth as an alternative, using the same IdP. Justin Dowswell Technology Coordinator Tenants' Union of NSW 02 8117 3721 On Fri, 30 Jun 2023 at 09:46, David Cook wrote: > Hey Justin, > > Sorry to hear you're having issues, but great to see another organisation > in NSW using Koha! > > Let's see if we can help you sort out this issue. What version of Koha are > you running, how did you install it, and on which Linux distro? > > With the Shibboleth, you'll want to look at your Koha logs. With the other > auth, are you using OAuth or OIDC? > > David Cook > Senior Software Engineer > Prosentient Systems > Suite 7.03 > 6a Glen St > Milsons Point NSW 2061 > Australia > > Office: 02 9212 0899 > Online: 02 8005 0595 > > -Original Message- > > Date: Wed, 28 Jun 2023 23:49:06 +1000 > From: Justin Dowswell > To: koha@lists.katipo.co.nz > Subject: [Koha] SSO Shibboleth & oauth issues > Message-ID: > < > cagzh+upebxvz2asoxmyyxhbctmy3mylh3ubpfvyqyzcrcqh...@mail.gmail.com> > Content-Type: text/plain; charset="UTF-8" > > Hey everyone, > > I am Justin from the Tenants’ Union of NSW. Lovely to meet you all, albeit > in an archaic manner. > > There is a Koha issue I am having trouble resolving… > > It’s a strange issue with Shibboleth and now I think the same issue > displayed differently with oauth (that I wanted to implement as an > alternative), both using the same IdP, and definitely isolated to Koha > and/or the server running it. I believe it’s a caching issue of some sort… > > When I get redirected back to Koha after a successful login with > Shibboleth, I get a HTTP 500 error, with this console output, unsure if > actually related or not: > > (index):6577 crbug/1173575, non-JS module files deprecated. (anonymous) @ > (index):6577 > > Refreshing the page redirects once again with a successful login. > > Oauth has a similar issue. I am redirected back to Koha after a > successful login with the identity provider and I am greeted with an error > message: > > > There was an error authenticating to external identity provider: > > wrong_csrf_token > > > Refreshing doesn't fix it but clicking the IdP login link again redirects > back with a successful login and token. > > My theory is the redirect is happening too quickly before the token is > actually retrieved. > > I've looked in Shibboleth's logs and have yet to see anything obvious. > > Thanks in advance, > Justin Dowswell > > -- > *The Tenants’ Union of NSW recognises that Aboriginal and Torres Strait > Islander peoples are the First Peoples of Australia. Our office is on the > lands of the Gadigal of the Eora Nation. We are committed to respecting > Aboriginal and Torres Strait Islander peoples, cultures, lands, and > histories as we battle for tenants’ rights in NSW. Read our full > Acknowledgement of Country > <https://www.tenants.org.au/tu/acknowledgement-country>.* > > > > > > <https://www.tenants.org.au/> > > tenants.org.au <https://www.tenants.org.au/> > > > <https://rentingfair.org.au> > > <https://www.facebook.com/TUNSW/> > <https://twitter.com/TUNSW> > <https://www.youtube.com/channel/UCEkW8D86OVVAV0QedKFhl9w> > > > > > > This email > transmission is intended only for the addressee and may contain > confidential or privileged information. Confidentiality and privilege are > not waived if you are not the intended recipient of the email, nor may you > use, review, disclose, disseminate or copy any information contained or > attached to it. If you received this email in error please delete it and > any attachments and notify us immediately by return email. > > Tenants' Union > of NSW can only provide information and advice in the New South Wales and > Commonwealth jurisdictions. If you are enquiring from another state or > territory please contact your local community legal centre. > > > > > > > > > -- *The Tenants’ Union of NSW recognises that Aboriginal and Torres Strait Islander peoples are the First Peoples of Australia. Our office is on the lands of the Gadigal of the Eora Nation. We are committed to respecting Aboriginal and Torres Strait Islander peoples, cultures, lands, and histories as we battle for tenants’ rights in NSW. Read our full Acknowledgement of Country <https://www.tenants.org.au/tu/acknowledgement-country>.* <https://www.tenants.org.au/> tenants.org.au <http
[Koha] SSO Shibboleth & oauth issues
Hey everyone, I am Justin from the Tenants’ Union of NSW. Lovely to meet you all, albeit in an archaic manner. There is a Koha issue I am having trouble resolving… It’s a strange issue with Shibboleth and now I think the same issue displayed differently with oauth (that I wanted to implement as an alternative), both using the same IdP, and definitely isolated to Koha and/or the server running it. I believe it’s a caching issue of some sort… When I get redirected back to Koha after a successful login with Shibboleth, I get a HTTP 500 error, with this console output, unsure if actually related or not: (index):6577 crbug/1173575, non-JS module files deprecated. (anonymous) @ (index):6577 Refreshing the page redirects once again with a successful login. Oauth has a similar issue. I am redirected back to Koha after a successful login with the identity provider and I am greeted with an error message: > There was an error authenticating to external identity provider: > wrong_csrf_token Refreshing doesn't fix it but clicking the IdP login link again redirects back with a successful login and token. My theory is the redirect is happening too quickly before the token is actually retrieved. I've looked in Shibboleth's logs and have yet to see anything obvious. Thanks in advance, Justin Dowswell -- *The Tenants’ Union of NSW recognises that Aboriginal and Torres Strait Islander peoples are the First Peoples of Australia. Our office is on the lands of the Gadigal of the Eora Nation. We are committed to respecting Aboriginal and Torres Strait Islander peoples, cultures, lands, and histories as we battle for tenants’ rights in NSW. Read our full Acknowledgement of Country <https://www.tenants.org.au/tu/acknowledgement-country>.* <https://www.tenants.org.au/> tenants.org.au <https://www.tenants.org.au/> <https://rentingfair.org.au> <https://www.facebook.com/TUNSW/> <https://twitter.com/TUNSW> <https://www.youtube.com/channel/UCEkW8D86OVVAV0QedKFhl9w> This email transmission is intended only for the addressee and may contain confidential or privileged information. Confidentiality and privilege are not waived if you are not the intended recipient of the email, nor may you use, review, disclose, disseminate or copy any information contained or attached to it. If you received this email in error please delete it and any attachments and notify us immediately by return email. Tenants' Union of NSW can only provide information and advice in the New South Wales and Commonwealth jurisdictions. If you are enquiring from another state or territory please contact your local community legal centre. ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
[Koha] Firefox pop up persistance
I did a system upgrade on friday before the end of the day. When I came into work on saturday and turned on our server (we shut it down at night for the time being), whenever I pull up a patron in the system, the "leave a message" box pops up and cannot be saved or cancelled in firefox. I can use koha in chrome with no issues but in firefox it happens every time with every patron. Ubuntu 14.04.5 LTS Koha 17.05.01.000 Not a real issue with our operations but still an issue. Justin Martin Library Assistant Abel J. Morneault Memorial Library ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
[Koha] backing up files after crash
So our server crashed (don't ask, it was my fault, I broke ubuntu) anyway, after a couple of days of getting lots of help from the folks in #ubuntu on freenode It is officially unresurectable. I can get chroot access and pull any files I may need off of it but I can't run a report of any kind. Is there a way for me to grab stuff for backup so I don't have to start from scratch? It's there just the OS is broken. Justin Martin Library Assistant Abel J. Morneault Memorial Library ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
[Koha] Bibliotheca integration
Our current library system for the state of Maine uses Overdrive for e-books and digital audiobooks. I am about to go live with our new KOHA system in a week or two. I just received an email stating that the state library system will be changing to Bibliotheca. http://www.bibliotheca.com/3/index.php/en-uk/ Until the official switch over we will be using the integrated overdrive features. I was curious if there is any plans of integration of this into KOHA? Until then I was curious if anyone has used the KOHA site to open links within the main frame while maintaining the menu's along the top and left? Or is it simply better to have it open in another window? Justin Martin Library Assistant Abel J. Morneault Memorial Library ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
[Koha] Koha system maintenace
Hi, I am wonder how you maintain your koha system? I'm trying to design a SOP for backup system. Once the system crashed, it will able to be recovered ASAP. What I am doing is run koha-run-backups everyday. If the system crashed, I will setup a new server and restore the latest backup files. But if I'm going to setup a new server, the latest version of koha will be used, which means I have to upgrade the koha system used currently according new version released. I wonder is there any risk if I always update my server to latest version. Can anyone share your system backup plan? Thanks, Justin ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] how to setup hold filled email notification?
Hi All, I'd searched this issue and found bug 9254 may be related to this issue. But what I need is how to enable hold filled email notification by on click instead of enable it one by one. Since we have lots of members already, it will be a big effort to enable it one by one. Can I modify it in MySQL database directly? which field to be modified? Thanks, Justin On Wed, Jun 24, 2015 at 2:18 PM, justin fang ccf...@gmail.com wrote: Hi All, I am trying to setup hold filled email notification. I found that I have to enable Enhancedmessagingpreferences first. After it is enabled, I will able to enable hold filledin Patron categories. BUT I have to enable it again for EVERY patron in his details page. Is it correct behavior? Can I enable hold filled notification in one click for all patrons? Thanks, Justin ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
[Koha] how to setup hold filled email notification?
Hi All, I am trying to setup hold filled email notification. I found that I have to enable Enhancedmessagingpreferences first. After it is enabled, I will able to enable hold filledin Patron categories. BUT I have to enable it again for EVERY patron in his details page. Is it correct behavior? Can I enable hold filled notification in one click for all patrons? Thanks, Justin ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] Koha SIP Server Loses Connection on 11 checkout request
Sebastian Hierl s.hierl@... writes: We just had a similar and previously unobserved issue with our RFID system (3M) -- checkout was delayed by up to 50 seconds. After a lot of testing and considering every possible issue with our data, such as date formats, duplicate userid, lack of cardnumbers, etc. and investigating every possible connection problem between the selfcheck machines and the server, we finally figured out the cause: 1) *some* of our patrons had an expiration date of and Koha took ca. 50 seconds to run date calculations on the expiration date... after lowering the expiration dates, the problem was solved. 2) this did not turn out to be the problem but may help to be aware of: the timeout period on our sip devices was set to 15 seconds--with Koha taking over 50 seconds to calculate the expiration date, the transaction failed. It was only after increasing the timeout period to one minute that we noticed that the transaction actually completed. In retrospect, it's all obvious. It would be good to store such experiences and resolutions somewhere so that the community can do a search and find solutions quickly. Sebastian -- Sebastian Hierl, Ph.D. Drue Heinz Librarian, Arthur Janet C. Ross Library American Academy in Rome Via Angelo Masina 5 00153 Rome Italy T: +39 06 5846 417 F: +39 06 5810 788 Thank you for your response. I checked the expiration date of the patrons and they are all set to 2023 so I don't believe it is the same issue. The connection seems to be lost instantly. When I send an incorrect SIP message, for example just 11 without any of the other required data I get the same result where the connection is dropped. I would expect a 96. Thanks Justin ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
[Koha] disallow hold requests to be placed on items that are not checked out
Hi, I have a question to setup disallow hold requests to be placed on items that are not checked out. I find a preference named AllowOnShelfHolds and it works. If the item is not checked out, I will unable to place a hold on it. BUT if the record has more than one items, I will ABLE to place a hold on it. For example, there is a record with three items, one of them are checkout but two are not. I will ABLE to place a hold on it. Is it correct behavior or is there any setting I missed? Thanks, Justin ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
[Koha] the definition of AllowOnShelfHolds?
I have a question regarding the option AllowOnShelfHolds. With the option, we will able to disallow hold requests to be placed on items that are not checked out. But in case of multiple items for one record, the rule seems not work. For example, we have 3 items for one record, one of the 3 items was checkout. User will be able place a hold on the item even 2 of them are not checkouted. Is this correct behavior? Thanks, Justin ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
[Koha] Koha SIP Server Loses Connection on 11 checkout request
, trimmed 1
character(s) (after chomps).
May 8 09:06:58 kohadebian koha_sip[3798]: INPUT MSG: '3520150508
090712AOCPL|AAC50085416D'
May 8 09:06:58 kohadebian koha_sip[3798]:
Sip::MsgType::new('Sip::MsgType', '3520150508...', '35'): seq.no '0',
protocol 2
May 8 09:06:58 kohadebian koha_sip[3798]:
Sip::MsgType::_initialize('End Patron Session', '20150508
090712AOCPL|AAC50085416D', 'A18', '18', ...)
May 8 09:06:58 kohadebian koha_sip[3798]: OUTPUT MSG: '36Y20150508
090658AOCPL|AAC50085416D|AFThank you !|'
May 8 09:06:59 kohadebian koha_sip[3798]: read_SIP_packet, INPUT MSG:
'6300120150508090714 AOCPL|AAC50085416D|'
May 8 09:06:59 kohadebian koha_sip[3798]: read_SIP_packet, INPUT MSG:
'6300120150508090714 AOCPL|AAC50085416D'
May 8 09:06:59 kohadebian koha_sip[3798]: read_SIP_packet, trimmed 1
character(s) (after chomps).
May 8 09:06:59 kohadebian koha_sip[3798]: INPUT MSG: '6300120150508
090714 AOCPL|AAC50085416D'
May 8 09:06:59 kohadebian koha_sip[3798]:
Sip::MsgType::new('Sip::MsgType', '6300120150...', '63'): seq.no '0',
protocol 2
May 8 09:06:59 kohadebian koha_sip[3798]:
Sip::MsgType::_initialize('Patron Info', '00120150508090714
AOCPL|AAC50085416D', 'A3A18A10', '31', ...)
May 8 09:06:59 kohadebian koha_sip[3798]: new ILS::Patron(C50085416D):
found patron 'C50085416D'
May 8 09:06:59 kohadebian koha_sip[3798]: patron_status_string:
C50085416D charge_ok: 1
May 8 09:06:59 kohadebian koha_sip[3798]: OUTPUT MSG: '64
00120150508090659AOCPL|AAC50085416D|AEKoha
Patron|BLY|CC5|BD10 Hall Road Sydney Australia|bet...@koha.com|BF0061
400 400 400|PB19670817|PCPT|PIY|AFGreetings from Koha. |'
May 8 09:07:02 kohadebian koha_sip[3798]: read_SIP_packet, INPUT MSG:
'11YN2015050809071720150508
090717AOCPL|AAC50085416D|ABA50136619B|AC|'
May 8 09:07:02 kohadebian koha_sip[3798]: read_SIP_packet, INPUT MSG:
'11YN2015050809071720150508
090717AOCPL|AAC50085416D|ABA50136619B|AC'
May 8 09:07:02 kohadebian koha_sip[3798]: read_SIP_packet, trimmed 1
character(s) (after chomps).
May 8 09:07:02 kohadebian koha_sip[3798]: INPUT MSG: '11YN20150508
09071720150508090717AOCPL|AAC50085416D|ABA50136619B|AC'
May 8 09:07:02 kohadebian koha_sip[3798]:
Sip::MsgType::new('Sip::MsgType', '11YN201505...', '11'): seq.no '0',
protocol 2
May 8 09:07:02 kohadebian koha_sip[3798]:
Sip::MsgType::_initialize('Checkout', 'YN2015050809071720150508
090717AOCPL|AAC50085416D|ABA50136619B|AC', 'CCA18A18', '38', ...)
I have also tried testing in the root terminal and all messages work
except the 11 message which returns:
Connection closed by foreign host.
Any help would be greatly appreciated.
Justin
___
Koha mailing list http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] unable to run fines.pl properly
Tomas Cohen Arazi tomascohen@... writes: How did you install Koha? And what user are you running Koha with? It sounds like you have set some environmental variables that point to the wrong db. Thanks for you hints. The issue is caused by incorrect setting in koha- conf.xml. It's solved. ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
[Koha] unable to run fines.pl properly
I have a koha system 3.16.4 running on ubuntu. I am trying to setup fine function. When bin/cronjobs/fines.pl executed, I got the following error. DBD::mysql::db selectrow_array failed: Table 'kohadata.systempreferences' doesn't exist at /usr/share/koha/lib/C4/Context.pm line 563. DBD::mysql::db selectrow_array failed: Table 'kohadata.systempreferences' doesn't exist at /usr/share/koha/lib/C4/Context.pm line 563. DBD::mysql::db selectrow_array failed: Table 'kohadata.systempreferences' doesn't exist at /usr/share/koha/lib/C4/Context.pm line 563. DBD::mysql::db selectrow_array failed: Table 'kohadata.systempreferences' doesn't exist at /usr/share/koha/lib/C4/Context.pm line 563. DBD::mysql::st execute failed: Table 'kohadata.issues' doesn't exist at /usr/share/koha/lib/C4/Overdues.pm line 140. Can't use an undefined value as an ARRAY reference at /usr/lib/perl5/DBI.pm line 2064. Does it mean something wrong with my database? Thanks, Justin ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
[Koha] Subject links not obeying 'UseAuthoritiesForTracings' setting
Hello, We're working on upgrading our instance of Koha from 3.6.4 to 3.14.7, and we've run into an issue with the UseAuthoritiesForTracings setting. It doesn't appear that Koha is obeying this setting, as we're seeing some subjects link to an:### searches instead of su:Words searches. The tricky part is that it's only some records, not all. It appears to be on a bib by bib basis. We're not actually using authorities at this point, but at some point in the past some authorities records were created. Is there something we're missing, or something we should be deleting to correct this? Justin -- *Justin Rittenhouse* *Sr. Application Development Technician, Web and Software Engineering* *Hesburgh Libraries* *University of Notre Dame* 208 Hesburgh Library ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
[Koha] CAS Authentication Errors
Hello, We're having issues setting up CAS on a new instance of Koha. We have this working on a 3.6.4 server, but we've implemented 3.14.5 on a new server and can't get it to accept the CAS ticket. The CAS server is returning a valid ticket, but the OPAC displays a (not obvious) error: Sorry, the CAS login failed. The following two lines appear in koha-opac-error_log: [Wed May 21 15:54:41 2014] [error] [client 10.41.57.78] [Wed May 21 15:54:41 2014] opac-user.pl: DBD::mysql::st execute failed: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '' at line 1 at /usr/share/koha/lib/C4/Letters.pm line 220. [Wed May 21 15:54:41 2014] [error] [client 10.41.57.78] [Wed May 21 15:54:41 2014] opac-user.pl: Can't use an undefined value as an ARRAY reference at /usr/local/lib64/perl5/DBI.pm line 2064. We've set up the CAS options to match the 3.6.4 server, and it sends the request to CAS appropriately, but it won't accept the response. Are we missing something? Thanks for any help, Justin -- *Justin Rittenhouse* *Sr. Application Development Technician, Web and Software Engineering* *Hesburgh Libraries* 208 Hesburgh Library o: 574-631-3065 e: jritt...@nd.edu ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] CAS Authentication Errors
Hello, Yes, I've confirmed the userid matches, and is identical to what we have set up on the 3.6.4 server. I wish it was that easy :-( Thanks for the suggestion though! On Thu, May 22, 2014 at 12:31 PM, Fridolin SOMERS fridolin.som...@biblibre.com wrote: Hie, Are you sure you have a borrower in Koha database with userid corresponding to CAS login ? Best regards, Le 22/05/2014 16:53, Justin Rittenhouse a écrit : Hello, We're having issues setting up CAS on a new instance of Koha. We have this working on a 3.6.4 server, but we've implemented 3.14.5 on a new server and can't get it to accept the CAS ticket. The CAS server is returning a valid ticket, but the OPAC displays a (not obvious) error: Sorry, the CAS login failed. The following two lines appear in koha-opac-error_log: [Wed May 21 15:54:41 2014] [error] [client 10.41.57.78] [Wed May 21 15:54:41 2014] opac-user.pl: DBD::mysql::st execute failed: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '' at line 1 at /usr/share/koha/lib/C4/Letters.pm line 220. [Wed May 21 15:54:41 2014] [error] [client 10.41.57.78] [Wed May 21 15:54:41 2014] opac-user.pl: Can't use an undefined value as an ARRAY reference at /usr/local/lib64/perl5/DBI.pm line 2064. We've set up the CAS options to match the 3.6.4 server, and it sends the request to CAS appropriately, but it won't accept the response. Are we missing something? Thanks for any help, Justin -- Fridolin SOMERS Biblibre - Pôles support et système fridolin.som...@biblibre.com ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha -- *Justin Rittenhouse* *Sr. Application Development Technician, Web and Software Engineering* *Hesburgh Libraries* 208 Hesburgh Library o: 574-631-3065 e: jritt...@nd.edu ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] Tag 100
Hi Michael, Generally those authority fields are locked so cataloguers can ensure everyone's only using the correct spellings and format for the fields. If you want to be able to edit 1XX fields directly in bib records, you need to turn on the ability. Under Koha Administration (Global) System Preferences if you go to the Authorities tab there is a preference entitled BiblioAddsAuthorities. Switch that to allow and save the Authorities preferences. You should be able to type in those locked 1XX fields now. (Speaking with my cataloguer's hat on, once you're out of testing it'd probably be best to leave that as don't allow so you don't have an untamed thistle patch of authority records. But maybe that's just me.) I hope that helped. Justin Unrau -- Prosentient Systems Pty Ltd http://prosentient.com.au 02-9212-0899 -Original Message- From: Michael Were mwe...@yahoo.com To: Koha@lists.katipo.co.nz Date: Mon, 9 May 2011 05:01:15 -0700 (PDT) Subject: [Koha] Tag 100 Hi Good People, I have installed koha on UBUNTU LTS 10.04 successfully,for testing purposes.My problem lies with tag 100,its field appears locked i cant type characters in that field!anyhelp will be appreciated. MICHAEL 0732677025 ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
