version upgrade for ckan2.9

Question

version upgrade for ckan2.9

liquanyong305 opened this issue 3 years ago · comments

Hello everyone

We use Ckan2.9.4 to develop our project, but ckan-oauth2 only supports 2.7 or 2.8.
Do you have any plans to upgrade version for ckan2.9?

Thanks a lot for the work you have done on this plugin.

Francesco Frassinelli · Answer 1 · Wed Feb 16 2022 17:56:44 GMT+0800 (China Standard Time)

Please test and give feedback to #46.

Nisha1293 · Answer 2 · Fri Aug 04 2023 19:25:55 GMT+0800 (China Standard Time)

Hi @frafra,

I tested #46 on latest CKAN v2.9.9 and v2.10.1 but I am getting below error:
AttributeError
AttributeError: 'Request' object has no attribute 'GET'

Any suggestion on this? Does any other PR exist, or are the latest changes in another branch?"

Francesco Frassinelli · Answer 3 · Sun Aug 06 2023 17:28:52 GMT+0800 (China Standard Time)

@nisha-nec See #42.

Nisha1293 · Answer 4 · Fri Sep 01 2023 17:48:35 GMT+0800 (China Standard Time)

Hi @frafra
Thanks for the information.
I tried but the code changes as per the CKANv2.9.x.
I tested it on CKANv2.10.1, in this version, Authentication logic to use [Flask-login] instead of repoze.who.
Do you have updated code. ?
Any help will be appreciated.

Francesco Frassinelli · Answer 5 · Mon Sep 04 2023 16:34:34 GMT+0800 (China Standard Time)

@nisha-nec I use this one with CKAN 2.9: https://github.com/NINAnor/ckanext-oauth2/tree/aeae71acd20dffd49a3eb7b084a32523859b3212

Nisha1293 · Answer 6 · Mon Sep 04 2023 16:39:53 GMT+0800 (China Standard Time)

@frafra yes, in 2.9 it will work fine, but from CKAN 2.10, Repoze has been replaced for flask-login and this includes several changes:

Login is now handled by user_login function (instead of set_repoze_user)
auth_tkt cookie has been deprecated since it was being set by Repoze

Francesco Frassinelli · Answer 7 · Mon Sep 04 2023 18:24:35 GMT+0800 (China Standard Time)

@nisha-nec Sorry for the misunderstanding. As you can see, no one seems interested in supporting OAuth2 on newer CKAN. Someone needs to pick up the PR for 2.9, fix the remaining issues, then merge the PR (or fork the repository), and then focus on the 2.10.