https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27305
--- Comment #7 from Nico Bako <[email protected]> --- Thanks a lot for the advice, David. > I'm not 100% sure what you mean by "API token" in this case. I'm thinking about how GitHub has "personal access tokens" https://docs.github.com/en/free-pro-team@latest/github/authenticating-to-github/creating-a-personal-access-token But that might be too complicated to implement, and probably unnecessary for a library system. > Koha already uses short-lived API tokens using OAuth2 for its HTTP API. I actually just checked this out, and I think you are referring to the REST-API instead of the SVC-API. I have tried using the REST-API, but I continue to get `{"error",:"Authentication failure."}`. Either I'm doing something wrong, or I just don't have access to some of the API endpoints. According to this page: https://wiki.koha-community.org/wiki/REST_api_RFCs#Unprivileged_.28public.29_routes it looks like I don't have access to much of the REST API; only privileged people can access them. Also, the iCal feed I am trying to get seems to only be available from the SVC API. > But since this is a case of one person exploiting a quirk in the system... > it's probably not a huge drama. And it is one that I hope will be closed in > the future ;). Haha. I'm proud of myself for being able to figure out how to connect my books' due dates with my Google calendar, but I'm not proud AT ALL of putting my password in the url... but you guys left me no other choice! -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug. _______________________________________________ Koha-bugs mailing list [email protected] https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
