Skip to content
This repository has been archived by the owner on Apr 26, 2024. It is now read-only.

Content repo should restrict access to users who can read the associated event (SYN-503) #1403

Closed
matrixbot opened this issue Oct 20, 2015 · 5 comments
Closed

Content repo should restrict access to users who can read the associated event (SYN-503) #1403

matrixbot opened this issue Oct 20, 2015 · 5 comments

Comments

@matrixbot
Copy link
Member

The ability for the media/content repo URLs to have access restricted to users who have an appropriate access_token to read the associated event has come up many times, but I can't find the bug, so filing a new one.

(Imported from https://matrix.org/jira/browse/SYN-503)

(Reported by @ara4n)
@matrixbot
Copy link
Member Author

Jira watchers: @ara4n

@matrixbot
Copy link
Member Author

matrixbot commented Oct 20, 2015 •
edited
Loading

Links exported from Jira:

relates to #1290

@matrixbot matrixbot changed the title Content repo could restrict access to users who can read the associated event (SYN-503) Content repo could restrict access to users who can read the associated event (https://github.com/matrix-org/synapse/issues/1403) Nov 7, 2016
@matrixbot matrixbot mentioned this issue Nov 7, 2016
Closed
@matrixbot matrixbot changed the title Content repo could restrict access to users who can read the associated event (https://github.com/matrix-org/synapse/issues/1403) Content repo could restrict access to users who can read the associated event (SYN-503) Nov 7, 2016
@ara4n ara4n changed the title Content repo could restrict access to users who can read the associated event (SYN-503) Content repo should restrict access to users who can read the associated event (SYN-503) Feb 10, 2017
@uhoreg uhoreg mentioned this issue Mar 21, 2017
Closed
@uhoreg uhoreg mentioned this issue Jul 6, 2017
Closed
@indefini indefini mentioned this issue Oct 16, 2017
Closed
@richvdh
Copy link
Member

richvdh commented Oct 16, 2017

#2103 duplicated this, but ended up with far more updates, so closing this in favour of it

@richvdh richvdh closed this as completed Oct 16, 2017
@user318
Copy link

user318 commented Oct 16, 2017

@richvdh, I did not look deep, but #2103 seems to have unrelated subject.

@richvdh
Copy link
Member

richvdh commented Oct 16, 2017

Good spot, thank you. I meant https://github.com/matrix-org/synapse/issues/2150.

@uhoreg uhoreg mentioned this issue Oct 16, 2017
Closed
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@user318 @richvdh @matrixbot