Dear Seafile and Community folkes,
I am trying to clear the content of a Seafile 11.0.4 library by using a BASH script and CURL calls against the Seafile server API.
So, naive as I am, I created an API Token from Web UI (by using triangle symbol on the library) having read and write permission and started to call the Seafile REST API.
The token is valid on some API endpoints, but lots of them can not be manipulated because they answer “invalid token”, so there must be a different type of token to access them.
I’ve got a hint that using Seafile Web API - web-api
(calling https://some-seafile-cloud-server-name.com/api2/auth-token/)
should give me an API token that is capable of interacting all the REST endpoints I yet can not access (even when I am Admin there).
But the problem is, all tutorials I found yet end up using a call like these:
curl -d "username=username@example.com&password=123456" https://cloud.seafile.com/api2/auth-token/
curl -d "username=username@example.com&password=123456" -H 'X-SEAFILE-OTP: <token>' https://cloud.seafile.com/api2/auth-token/
As stated in the link of home.md above.
As I am using keycloak on my private server, which ist the only active authentication method there, it is not possible to use username and password or the X-SEAFILE-OTP Header, because keycloak is doing the job.
How to go on, any ideas?
Am I on the right track?
Have a nice day!
Sunny