We need to resurrect it, yes. We need to keep the idea of allowing API/key management (add/delete/revoke) and provide basic authentication (though headers) using those.
I mean the first patches from Julian, not the whole patchset that requires a full Auth.pm rewrite/refactoring. Martin was wroking on an Oauth2 implementation, but for trusted consumers, it would be ok to use basic authentication through an SSL connexion. Regards El jue., 11 may. 2017 a las 10:49, Paul Poulain (<paul.poul...@biblibre.com>) escribió: > Hi all, > > Matthias is working on connecting Koha and Coral, and he's facing some > problems with authentication. We need to authenticate and use a session > cookie, that's not easy. Could we find another solution ? Should we > revive bz 13920 ? > (https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13920) > > Suggestions/ideas welcomed ! > > > -- > Paul Poulain, Associé-gérant / co-owner > BibLibre, Services en logiciels libres pour les bibliothèques > BibLibre, Open Source software and services for libraries > > _______________________________________________ > Koha-devel mailing list > Koha-devel@lists.koha-community.org > http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ > git : http://git.koha-community.org/ > bugs : http://bugs.koha-community.org/ -- Tomás Cohen Arazi Theke Solutions (https://theke.io <http://theke.io/>) ✆ +54 9351 3513384 <+54%209%20351%20351-3384> GPG: B2F3C15F
_______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
