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

Using Vue.js in Koha plugins
by David Cook 23 Mar '23

23 Mar '23

Hey Jonathan, Do you think it would be possible to use Vue.js in Koha plugins? I haven't played with webpack but it looks like "koha-tmpl/intranet-tmpl/prog/js/vue/dist/erm.js" contains the entirety of Vue.js in itself, so in theory it would be possible to include whatever Vue.js on a different page that doesn't load erm.js. Have we thought about separating out the core Vue.js library from the Vue.js application code using the SplitChunksPlugin? That way we could include the vue.js library code wherever we might want it, and only load the erm.js application code on the ERM page(s). Perhaps we could split other re-usable components out as well. Of course, the Koha plugin would be implementing its Vue.js application without a build step. But I think that would be OK. I'm thinking of a scenario where the Koha plugin provides data via an API endpoint, and wants to display that data using a Koha Vue DataTable for instance. What do you think? 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

3 5

Mojolicious::Plugin::OAuth2 only uses client_secret_post client authentication method
by David Cook 19 Mar '23

19 Mar '23

Hi all, I can't remember if I've said this before but it looks like Mojolicious::Plugin::OAuth2 only uses the client_secret_post client authentication method. In the OpenID Connect spec, "client_secret_basic" is actually the default method: https://openid.net/specs/openid-connect-core-1_0.html#ClientAuthentication I think that Keycloak checks both the Authorization header and the request body, which is probably why it's worked so easily with the Koha OpenID Connect auth. I couldn't find any documentation on this for Keycloak, but I think it's a safe assumption. Reported the issue on Github: https://github.com/marcusramberg/Mojolicious-Plugin-OAuth2/issues/72. Really it should be a very straight forward change to implement in the plugin. 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

1 0

Call for news - Newsletter March 2023
by Koha Newsletter 12 Mar '23

12 Mar '23

Hi I'm collecting news for the March 2023 Koha Community Newsletter. Please send anything noteworthy to: kohanews (at) gmail (dot) com News criteria: * News items can be of any length. * Images are fine. * Anything and everything Koha. * Submit by the 26th of the month. Text format criteria: * Just structured plain text, or * HTML text to include tables or similar For events: * Consider adding your event to the Koha Community calendar at https://koha-community.org/calendar/ Thank you! Michael Kuhn Editor, Koha Community Newsletter

1 0

Easiest sign off in the world (BZ 33189 plugin upload prompt for .kpz files)
by David Cook 09 Mar '23

09 Mar '23

Hi all, I was going to upload a Koha plugin today when I was bemoaning having to sift through all my Downloads entries to find the .kpz file I wanted. Then I remembered that input type="file" actually allows you to specify what files to look for using the "accept" attribute. So I wrote a little patch for the Koha plugin upload, and it's soooo much nicer now. Anyone looking for the world's easiest/fastest sign off, please go and check it out. Thanks! 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

1 0

Using "ucf" to manage log4perl.conf
by David Cook 09 Mar '23

09 Mar '23

Hi all, I've attached an "alternative" patch on "Bug 32791 - Log4perl configuration files need a tool for updating on package upgrade". It uses the utility "ucf" to manage log4perl.conf. It works well for handling upgrades to log4perl.conf configuration, but it needs more testing and some more consideration for koha-create, koha-remove, and apt-get purge. Is anyone else interested in working on this with me? 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

2 2

Fixing perltidy in ktd
by David Cook 09 Mar '23

09 Mar '23

Hi Tomas, I saw you, Katrin, and Jonathan writing in #koha about perltidy. When I've tried previously to perltidy in ktd using the ":Tidy" command, it seemed to change the style to something incompatible with https://wiki.koha-community.org/wiki/Coding_Guidelines If I type "vi Koha.pm", then ":echo $MYVIMRC", it tells me I'm using the /root/.vimrc file. I'm not overwriting that, so it's the default file that ships with ktd. I don't have a good example off the top of my head though. I've just tried perltidying debian/scripts/koha-log4perl from https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32791. There are things that look weird to me but after reviewing the coding guidelines, maybe I've been wrong all this time. For example: - my $snippet = get_snippet({ - instance => $instance, - component => $component, - }); - if ($snippet){ + my $snippet = get_snippet( + { + instance => $instance, + component => $component, + } + ); I always thought we preferred to keep the brackets on the same line (like in all the JS examples on the wiki). It looks like perltidy sometimes mangles the whitespace for comments as well. I'd correctly indented a comment and then perltidy stripped all the whitespace except for 2 leading spaces. That all said. overall it probably does look better, so maybe the out of the box perltidy is good enough, and if the same perltidy file is applied across the board I suppose it doesn't matter. 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

3 3

Not ignoring you...
by David Cook 09 Mar '23

09 Mar '23

Hi all, Looks like a number of you have been sending emails and it probably seems like I've ignored you. but it turns out they've been going to my Junk Mail. Sorry about that! 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

1 0

Re: [Koha-devel] help: // Koha rest api error (401)
by Eric Phetteplace 09 Mar '23

09 Mar '23

Hi Esharat, You should keep the listserv copied on replies so others can see the conversation, learn from it, or respond. I don't know what the issue could be then. Are you performing the same requests from the RESTer extension, as in first getting a token and then using it in an authorization header? Small note, 443 isn't a subdomain, it's a port number. Your request would look like: response = requests.get(f"https://{mydomain}:443/api/v1/quotes", headers=auth2) but it is also more likely to be 8443 if your HTTP port is 8080. But if the RESTer client works with whatever you're doing, then the ports are not the issue. As I said, your code works for me as written, and if another client successfully requests something from your server then it is configured correctly. If you are not sharing the exact code you're running, that might help, or if you show the actual response data (a 401 should still have some data encoded in it) or any error stack traces. Best, ERIC PHETTEPLACE Systems Librarian, Libraries (he/him) ephetteplace(a)cca.edu *CCA is situated on the traditional unceded lands of the **Chochenyo and Ramaytush Ohlone** peoples.* Black-owned bookstores in Oakland: Ashay by the Bay <https://ashaybythebay.com/>, Marcus Books <https://www.facebook.com/marcus.books/> :(){ :|: & };: On Tue, Mar 7, 2023 at 9:04 AM Esharat Mia <esharat(a)esharat.me> wrote: > Dear Phetteplace, > Hope you are well. Thank you so much for your response. > I tried with 443 with sub domain. But I faced same issues. For your kind > information, I tested my api using RESTer chrome extension, it worked. I > enable all api setting from koha adminstration. Need any editional > configuration in server side? > > > ---- On Tue, 07 Mar 2023 22:56:23 +0600 * ephetteplace(a)cca.edu > <ephetteplace(a)cca.edu> * wrote ---- > > Hi Esharat, > > Your code should work but it has a few things that don't make sense. > > Are you sure you have the setting "RESTOAuth2ClientCredentials" on your > Koha? That is one guess. > > My other thought is that you are requesting an HTTPS resource from a URL > on port 8080. This looks like you might be running Koha locally; usually, > HTTP requests are to port 80 and HTTPS to 443 and when you run things > locally those are often shifted up eight thousand spots to 8080 and 8443. > So basically—are you sure your server sends HTTPS responses on port 8080? > Are you able to load https://{mydomain}:8080 in a browser? You said > you're getting a 401 error, which means you're get a response, so this > seems unlikely to be the problem (you would see a connection error and not > receive a response if it was). > > I was able to test successfully with your code so I don't necessarily > think these are issues either, but there are a few pieces that don't make > sense. The HTTPS connection that's initialized at the top is never used. As > far as I know, the requests library doesn't magically pick up an existing > connection and use it, nor is this necessary (requests will make a > connection for you). Also, your second request uses a "content-type: > application/json" HTTP header but it is a GET request, content-type is a > header for *the type of data you're sending* but GET requests do not send > anything. You probably meant to have an "accept: application/json" header > instead. But again, I tried on our instance with that code and Koha did not > seem to mind. > > Best, > > ERIC PHETTEPLACE Systems Librarian, Libraries (he/him) > > ephetteplace(a)cca.edu > > > *CCA is situated on the traditional unceded lands of the **Chochenyo and > Ramaytush Ohlone** peoples.* > > Black-owned bookstores in Oakland: Ashay by the Bay > <https://ashaybythebay.com/>, Marcus Books > <https://www.facebook.com/marcus.books/> > > :(){ :|: & };: > > > On Tue, Mar 7, 2023 at 12:59 AM Esharat Mia <esharat(a)esharat.me> wrote: > > Dear All, > Hope this email finds you well. I am facing a error koha rest api , I > explained below - > I use the below code base for the koha rest api . When I check the bywater > koha demo site's rest api, it's working fine but When I checked my demo > koha site, getting authentication error(401) > I entered the correct client id and secret ssl certificate installed > correctly. My api worked properly using the chrome *RESTer* tool. Thanks > in advance . > > *import requests* > *import json* > *import os* > *from requests.structures import CaseInsensitiveDict* > *import http.client* > *conn = http.client.HTTPSConnection("http://123.49.46.157:8080/ > <http://123.49.46.157:8080/>")* > > *#from dotenv import load_dotenv* > > *#load_dotenv()* > *data = {* > *"client_id": "e877bce0-78bc-4d39-a0c1-2df7fccb1397",* > *"client_secret": "461cda1a-665d-4d24-a0e0-dace5f83a1f4",* > *"grant_type": "client_credentials",* > > *}* > > *response = requests.post > <http://requests.post>("http://123.49.46.157:8080/api/v1/oauth/token > <http://123.49.46.157:8080/api/v1/oauth/token>", data=data)* > > *credentials = response.json()* > *print(credentials)* > *access_token = credentials['access_token']* > *print("Access_token: ",access_token)* > *#auth2 = CaseInsensitiveDict()* > *auth2={"content-type":"application/json","authorization": f"Bearer > {access_token}"}* > > *print(auth2)* > *response = requests.request("GET", > "http://123.49.46.157:8080/api/v1/patrons > <http://123.49.46.157:8080/api/v1/patrons>", headers=auth2* > *)* > > *print(response)* > > Regrads, > Esharat Mia > > > _______________________________________________ > Koha-devel mailing list > Koha-devel(a)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/ > > >

2 2

Koha rest api error
by Esharat Mia 07 Mar '23

07 Mar '23

Dear All, Hope this email finds you well. I am facing a error koha rest api , I explained below - I use the below code base for the koha rest api . When I check the bywater koha demo site's rest api, it's working fine but When I checked my demo koha site, getting authentication error(401) I entered the correct client id and secret ssl certificate installed correctly. My api worked properly using the chrome RESTer tool. Thanks in advance . import requests import json import os from requests.structures import CaseInsensitiveDict import http.client conn = http.client.HTTPSConnection("http://123.49.46.157:8080/") #from dotenv import load_dotenv #load_dotenv() data = { "client_id": "e877bce0-78bc-4d39-a0c1-2df7fccb1397", "client_secret": "461cda1a-665d-4d24-a0e0-dace5f83a1f4", "grant_type": "client_credentials", } response = requests.post("http://123.49.46.157:8080/api/v1/oauth/token", data=data) credentials = response.json() print(credentials) access_token = credentials['access_token'] print("Access_token: ",access_token) #auth2 = CaseInsensitiveDict() auth2={"content-type":"application/json","authorization": f"Bearer {access_token}"} print(auth2) response = requests.request("GET", "http://123.49.46.157:8080/api/v1/patrons", headers=auth2 ) print(response) Regrads, Esharat Mia

2 1

Request for signoff
by Marcel de Rooy 03 Mar '23

03 Mar '23

Hi all, I could use some help getting two patches further: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32334 Sync comments in database with schema https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32426 Allow plugin to generate userid when creating patrons Thanks in advance, Marcel

1 0