feature request - support public shared folders

[veselov]

Hello!

It would be nice if the access to shared public folders was supported as well.
In our case, we expose those to certain entities, for either upload or download.
However, some of the handled binaries can be quite large, and we see upload failures in the browser.

[cdujeu]

hello @veselov can you be more specific for describing the failures?
Do you see usecases working via "standard" access whereas failing when going through public links ?
Can you give a proper scenario for reproducing the issue ?

[veselov]

There are no failures.
I'm talking about public folders - access points that are created for distributing off of a particular sub-folder of a cell. Creating those issue a separate URL, and a password (no username).

Now, if all I have is such a link, and a password, I can't ask the client to authenticate against it, and then exchange files back and forth. The current authentication methods don't support that kind of authentication, not that I can see. If nothing else, the username is required, but that's not available for these links.

[cdujeu]

Hi @veselov sorry for not coming on this - are you still waiting some hints on that topic ?

[veselov]

AFAIU, public folders aren't supported, hence this is a feature request.
Are there any questions about my earlier explanation?

[cdujeu]

yes it was clear.
In fact you could use it, but it's just that the way to retrieve the proper login password to connect is a bit hacky. Are you familiar with the developer console in the browser ? ;-)

[veselov]

Interesting.
I see that the browser makes the following request:

POST https://<hostname>/a/frontend/session

{"AuthInfo":{"login":"d09***","password":"bZ***","type":"credentials"}}

replied to with a JWT token.

I see that request is followed up by a GET to https://<hostname>/a/frontend/state?, which includes a cookie that is probably somehow encoded token; the response is 200, is an XML document with <pydio_registry> root.

I can also see that the login doesn't change between consecutive attempts to log in (but not sure how is it derived from the URL).

However, when I try to configure the cec client with these creds, I get an error:

[vps@phoenix]~/tmp$ cec config add
✔ Client Auth (direct login/password, less secure)
Server Address (provide a valid URL): https://<hostname>/
✔ No
User Login: d09***
User Password: ************
2025/02/24 12:48:24 ... Authenticated request failed, cause: Get "https://<hostname>/a/frontend/state": [POST /frontend/session][401] frontSessionUnauthorized {"Detail":"Unauthorized: Login failed","Title":"Login failed"}
2025/02/24 12:48:24 ✗ could not save configuration: could not connect to distant server with provided parameters. Discarding change

So yes, I'd appreciate some hints on this.