[Koha-devel] TLS connections

[Jacob Jett]

Hi gang,

It looks like AWS is upgrading their TLS connections from 1.0/1.1 to 1.2.
Does anyone know if this will impact Koha records that point at AWS objects?

Unrelated ISBD punctuation question. I've had some complaints from my staff
about displaying ISBD punctuation. We use it in MARC to make sure that the
metadata records are portable across multiple languages. However, I can
sympathize that it doesn't look very clean in the display. Is there a Koha
widget that either, let's us suppress displaying the ISBD punctuation or
implements it at metadata record export time?

Regards,

Jacob

*Jacob Jett* | Research Librarian | ASFPM
8301 Excelsior Dr.  | Madison, WI  53717
tel: 608-828-3000  | desk: 608-828-6342 | floods.org
 | *Email Jacob *
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : https://www.koha-community.org/
git : https://git.koha-community.org/
bugs : https://bugs.koha-community.org/

Re: [Koha-devel] TLS connections

[David Cook]

Hi Jacob,

 

Most servers should already be using TLS 1.2, and all modern browsers should 
support it, so it’s all good. 

 

As for the ISBD, in terms of display, you could use custom XSLTs to change the 
display, but a maintenance burden would come with that for you. I don’t think 
there’s a way to transform metadata at export time.

 

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: Koha-devel  On Behalf Of 
Jacob Jett
Sent: Tuesday, 23 May 2023 12:59 AM
To: koha-devel@lists.koha-community.org
Subject: [Koha-devel] TLS connections

 

Hi gang,

 

It looks like AWS is upgrading their TLS connections from 1.0/1.1 to 1.2. Does 
anyone know if this will impact Koha records that point at AWS objects?

 

Unrelated ISBD punctuation question. I've had some complaints from my staff 
about displaying ISBD punctuation. We use it in MARC to make sure that the 
metadata records are portable across multiple languages. However, I can 
sympathize that it doesn't look very clean in the display. Is there a Koha 
widget that either, let's us suppress displaying the ISBD punctuation or 
implements it at metadata record export time?

 

Regards,

 

Jacob

 

Jacob Jett | Research Librarian | ASFPM 
8301 Excelsior Dr.  | Madison, WI  53717
tel: 608-828-3000  | desk: 608-828-6342 |   floods.org 
| Email Jacob   

___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : https://www.koha-community.org/
git : https://git.koha-community.org/
bugs : https://bugs.koha-community.org/

Re: [Koha-devel] Placing multiple record-level holds on a record

[David Cook]

Hi Katrin,

 

But I think the intention of “Holds per record (count)” was to enable multiple 
item-level holds rather than multiple record-level holds? 
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14695

 

I suppose one could argue though that record-level holds are ultimately still 
for items… but (depending on your rules) you can place 1+ record-level holds on 
a record with only 1 item (e.g. I have 10 holds on 1 record that has 1 item). 
If you have item-level holds, you can only ever place 1 item-level hold on that 
1 item. It looks like a loophole/flaw to me. 

 

You can also place holds on items you already have checked out which seems 
weird. (I think it’s probably due to the syspref AllowHoldsOnPatronsPossessions 
although I think the intention there was probably to allow holds on other items 
belonging to that record.)

 

I haven’t thoroughly tested it, but I think in theory you could monopolize an 
item for longer than a library intends if the circ rules were loose. 

 

I suppose I was just wondering if these are intentional or accidental 
behaviours. Holds are tricky though. What I might see as a bug might be a 
feature to someone else…

 

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: Koha-devel  On Behalf Of 
Katrin Fischer
Sent: Monday, 22 May 2023 3:19 PM
To: koha-devel@lists.koha-community.org
Subject: Re: [Koha-devel] Placing multiple record-level holds on a record

 

hi David,

it depends, there is definitely a feature to do that. If you can place multiple 
per record is defined in the circulation rules. If holds per record is 1, you 
should of course not be able to. It's been there for multiple versions now.

Hope that helps,

Katrin

On 22.05.23 06:46, David Cook wrote:

Hi all,

 

I’m noticing in 22.11 that it’s possible to place multiple record-level holds 
on a record.

 

Do you think that’s intentional? While I can understand having multiple 
item-level holds, having multiple record-level holds seems like a way to game 
the system…

 

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

 





___
Koha-devel mailing list
Koha-devel@lists.koha-community.org 
 
https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : https://www.koha-community.org/
git : https://git.koha-community.org/
bugs : https://bugs.koha-community.org/

___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : https://www.koha-community.org/
git : https://git.koha-community.org/
bugs : https://bugs.koha-community.org/

Re: [Koha-devel] Azure configuration for OAuth authentication with Koha

[David Cook]

Hi Alex,

Well, the good news is that OIDC is just a wrapper around OAuth2, so a lot of 
the same things apply either way.

But my experience using only OAuth2 for AuthN is pretty limited. Previously, 
I've reviewed how Keycloak integrates with OAuth2 endpoints for things like 
Facebook: 
https://github.com/keycloak/keycloak/blob/main/services/src/main/java/org/keycloak/social/facebook/FacebookIdentityProvider.java

Sounds like you're making progress though.

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-
From: Alex Buckley  
Sent: Monday, 22 May 2023 3:23 PM
To: David Cook ; 'koha-devel' 

Subject: Re: [Koha-devel] Azure configuration for OAuth authentication with Koha

Hi David,

Ah that might be the problem! The client is using OAuth with Azure currently. 
We have indeed set up using OIDC with Azure before, but we haven't used OAuth 
before with any identity providers.

Thanks for raising that. Are you aware of what IdP OAuth should be used with?

Kind regards,

Alex


On 22/05/23 11:27, David Cook wrote:
> Hi Alex,
>
> Do you mean OAuth or OIDC? With Azure you'd want to be using OIDC which I 
> think you folk have set up before with Azure?
>
> When it comes to the URIs you register, you'll want to use a * wildcard at 
> the end of the OpacBaseURL, so that the users are able to login from any page 
> in the Koha OPAC.
>
> 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-
> From: Koha-devel  On 
> Behalf Of Alex Buckley
> Sent: Monday, 22 May 2023 6:26 AM
> To: koha-devel 
> Subject: [Koha-devel] Azure configuration for OAuth authentication 
> with Koha
>
> Hi Koha community,
>
> If you have configured Koha OAuth authentication with Azure could you please 
> let me know what did you configure as the Redirect and Reply URIs in Azure?
>
> Context: We have a library (running Koha 22.11) that is trying to setup OAuth 
> authentication with Azure.
>
> They have configured the Koha end using the new Koha 'Administration' > 
> 'Identity provider' pages.
>
> When this library attempt a SSO login they get a 'AADSTS00113: No reply 
> address is registered for the application' Azure error - see attached.
>
> Should the Redirect and Reply URIs in Azure just be the Koha OpacBaseURL 
> (with https), or something else?
>
> Thanks so much,
>
> Alex
>
--
Alex Buckley
Koha Developer | Implementation Lead
Catalyst.Net Limited - Expert Open Source Solutions

Catalyst.Net Limited - a Catalyst IT group company

CONFIDENTIALITY NOTICE: This email is intended for the named recipients only. 
It may contain privileged, confidential or copyright information. If you are 
not the named recipient, any use, reliance upon, disclosure or copying of this 
email or its attachments is unauthorised. If you have received this email in 
error, please reply via email or call +64 4 499 2267.

___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : https://www.koha-community.org/
git : https://git.koha-community.org/
bugs : https://bugs.koha-community.org/