Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[OCM] Users can invite themselves to their own federated connection #11004

Open
PrajwolAmatya opened this issue Feb 13, 2025 · 2 comments · May be fixed by #11097
Open

[OCM] Users can invite themselves to their own federated connection #11004

PrajwolAmatya opened this issue Feb 13, 2025 · 2 comments · May be fixed by #11097
Assignees
Labels

Comments

@PrajwolAmatya
Copy link
Contributor

PrajwolAmatya commented Feb 13, 2025

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.

Image

Image

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

@saw-jan
Copy link
Member

saw-jan commented Feb 13, 2025

CC @kobergj @2403905

@PrajwolAmatya
Copy link
Contributor Author

We are currently getting 400 status code with following response:

{
  "code": "INVALID_PARAMETER",
  "message": "token has expired"
}

The error message doesn't match the error message added in this PR cs3org/reva#5077.

CC @2403905

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: Needs Tests
Development

Successfully merging a pull request may close this issue.

3 participants