Open
Description
Describe the bug
When a user generates a token for federated connection and pastes it to their own accept invitation field, then a federated connection is created with the user itself.
Video Demonstration
Screencast.from.02-13-2025.02.05.15.PM.webm
Here we can see that a federated connection is created with the user himself and while sharing a resource, an external user is also available and resources can also be shared. The shared resource is available on your own shares drive.
Also, an error does show up, but nothing is restricted for federation connections.
The behavior is same when creating connection using API
curl -kv -uadmin:admin "https://localhost:9200/sciencemesh/accept-invite" -XPOST \
--data '{
"providerDomain": "localhost:9200",
"token": "<token>"
}'
This returns the following response and 409
status code:
{
"code": "ALREADY_EXIST",
"message": "user already known"
}
Eventhough it throws error, the connection is created.
Setup
Infinite Scale 7.1.0-rc.4+ac1689b64d Community
ownCloud Web UI 11.1.3
Metadata
Metadata
Assignees
Labels
Type
Projects
Status
Needs Tests