[Koha-bugs] [Bug 14868] REST API: Swagger2-driven permission checking
bugzilla-daemon at bugs.koha-community.org
bugzilla-daemon at bugs.koha-community.org
Thu Jun 30 15:54:22 CEST 2016
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14868
Johanna Räisä <johanna.raisa at gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #52995|0 |1
is obsolete| |
--- Comment #21 from Johanna Räisä <johanna.raisa at gmail.com> ---
Created attachment 52996
-->
https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=52996&action=edit
[SIGNED-OFF] Bug 14868: Rename 'x-koha-permission' to 'x-koha-authorization'
Since we need to be able to define other authorization options than simply Koha
permissions, for example "allow-owner", we should rename x-koha-permission into
x-koha-authorization to better describe the object.
This patch simply renames all occurences of x-koha-permission into
x-koha-authorization.
The new specification for authorization:
"/patrons/{borrowernumber}": {
..
"x-koha-authorization": {
"allow-owner": "1",
"pemissions": {
"borrowers": "1"
}
}
}
Signed-off-by: Olli-Antti Kivilahti <olli-antti.kivilahti at jns.fi>
My name is Olli-Antti Kivilahti and I approve this commit.
We have been using the Swagger2.0-driven REST API on Mojolicious for 1 year now
in production and I am certain we have a pretty good idea on how to work with
the limitations of Swagger2.0
We participated in the development of the Mojolicious::Plugin::Swagger and know
it well. We have made an extension to the plugin to provide full CORS support
and have been building all our in-house features on the new REST API.
Signed-off-by: Johanna Raisa <johanna.raisa at gmail.com>
My name is Johanna Räisä and I approve this commit.
We have been using Swagger2.0-driven REST API in production successfully.
--
You are receiving this mail because:
You are watching all bug changes.
More information about the Koha-bugs
mailing list