CSRF token authorization not correctly implemented about churchtoolsapi HOT 3 CLOSED

Let's find the issue first before adding this to init ...
I'm not getting this issue on my system but will try to verify my tests against your system as part of this bug report.

Thanks for providing login details for testing!

from churchtoolsapi.

@kolibri52 - i can't reproduce your bug.
I've tried with the credentials you provided and both
test_login_ct_ajax_api
and
test_login_ct_rest_api
did succeed after removing some hardcoded which generated the success message only for a specifc user ID ... maybe this was the issue on your instance too?

feel free to pull the changes from master into your working branch in order to check.

• please lock my test acount on your system i think i no longer need it at this point.

from churchtoolsapi.

executing

def test_file_download(self):

without any prior code execution
succeeds on elkw1610.krz.tools succeeds with arrangement ID 762

but returns
'CSRF-Token is invalid'
on https://lgv-oe.church.tools/

folloewd by
WARNING:root:File test.txt does not exist

Assumption - https://hilfe.church.tools/wiki/0/API-CSRF?search=csrf - CSRF is disabled on KRZ.tools ...

from churchtoolsapi.