Age | Commit message (Collapse) | Author |
|
Signed-off-by: Joas Schilling <coding@schilljs.com>
|
|
Signed-off-by: Jakob Röhrl <jakob.roehrl@web.de>
|
|
Signed-off-by: Joas Schilling <coding@schilljs.com>
|
|
Signed-off-by: Joas Schilling <coding@schilljs.com>
|
|
Signed-off-by: Joas Schilling <coding@schilljs.com>
|
|
Signed-off-by: Joas Schilling <coding@schilljs.com>
|
|
Signed-off-by: Joas Schilling <coding@schilljs.com>
|
|
Signed-off-by: Joas Schilling <coding@schilljs.com>
|
|
Signed-off-by: Joas Schilling <coding@schilljs.com>
|
|
Signed-off-by: Joas Schilling <coding@schilljs.com>
|
|
Signed-off-by: Joas Schilling <coding@schilljs.com>
|
|
Signed-off-by: Vincent Petry <vincent@nextcloud.com>
|
|
Signed-off-by: Vincent Petry <vincent@nextcloud.com>
|
|
Signed-off-by: Joas Schilling <coding@schilljs.com>
|
|
Fix the test to actually use the variable from the example list.
Signed-off-by: Vincent Petry <vincent@nextcloud.com>
|
|
Until now no scheme could be configured to connect to the TURN server
and "turn:" was used by default. The "turns:" scheme defines a
connection over TLS, which in some cases is needed by clients behind a
very restrictive firewall that only allows TLS connections. However,
encrypted TURN connections also require a certificate to be set in the
TURN server, which may not be always available. Moreover, encrypted TURN
connections also require a domain. Due to all this now it is possible to
set the TURN server scheme to "turn:", "turns:" or both, so the
administrator can set the best suiting one.
Already configured TURN servers that have no scheme configured yet
defaults to "turn:" to keep the same behaviour as before. New configured
TURN servers also default to "turn:", as "turns:" has some additional
requirements as explained above.
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
|
|
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
|
|
Signed-off-by: Joas Schilling <coding@schilljs.com>
|
|
Signed-off-by: Joas Schilling <coding@schilljs.com>
|
|
Updated wording for conversation visibility
|
|
nextcloud/add-mapping-between-nextcloud-session-id-and-signaling-server-session-id
Add mapping between Nextcloud session id and signaling server session id
|
|
When the internal signaling server is used the Nextcloud session id and
the signaling session id are the same. However, if the external
signaling server is used they are different.
Signaling messages for participants in calls (like joining the call,
muting and so on) are identified only by their signaling session id, so
when the external signaling server is used it was not possible to
associate participants in calls with the participant information
provided by the Nextcloud server.
However, when a participant joins a call her client notifies the
Nextcloud server (either directly or, in the case of SIP clients,
through the signaling server). The Nextcloud server then notifies the
signaling server which, in turn, notifies all the clients. When
Nextcloud notifies the signaling server the participant is identified
with the Nextcloud session id, and the signaling server then replaces
that with the signaling session id before relaying the message to the
clients.
Due to this when a participant joins (or leaves) a call now the
Nextcloud session id is sent too in an extra property. This property is
not adjusted by the external signaling server, so the clients receive
both the signaling session id and the Nextcloud session id and thus are
able to map them.
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
|
|
Signed-off-by: Joas Schilling <coding@schilljs.com>
|
|
Signed-off-by: Vincent Petry <vincent@nextcloud.com>
|
|
Signed-off-by: Joas Schilling <coding@schilljs.com>
|
|
Signed-off-by: Joas Schilling <coding@schilljs.com>
|
|
Signed-off-by: Roeland Jago Douma <roeland@famdouma.nl>
|
|
Signed-off-by: Joas Schilling <coding@schilljs.com>
|
|
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
|
|
nextcloud/remove-undefined-variable-from-spreedcheats-controller-cleanup
Remove undefined variable from spreedcheats controller cleanup
|
|
This is a leftover from c0358096b3e5
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
|
|
Added capability to signal the existence of the v3 API.
Signed-off-by: Vincent Petry <vincent@nextcloud.com>
|
|
Signed-off-by: Vincent Petry <vincent@nextcloud.com>
|
|
Removed cheat that used GuestManager directly from the guests app.
Now using occ guests:add to create guest account users.
Signed-off-by: Vincent Petry <vincent@nextcloud.com>
|
|
Seems PHP CS fixer has some new rules or operations.
This fixes the code to match the new rules by running composer run
cs:fix.
Signed-off-by: Vincent Petry <vincent@nextcloud.com>
|
|
Signed-off-by: Vincent Petry <vincent@nextcloud.com>
|
|
nextcloud/bugfix/noid/allow-to-respond-with-modified-common-read-value
Allow to respond with modified common read value on "not modified" messages
|
|
We need to set the status code to 200 when the header is modified,
because as per "section 10.3.5 of RFC 2616" entity headers shall be
stripped out on 304: https://stackoverflow.com/a/17822709
This means the header would not be sent to the clients at all, so
they wouldn't update the read marker when idling in the chat.
For the web interface this is not needed, as we update the info
every 30 seconds with the conversation list refresh and can therefor
save the query
Signed-off-by: Joas Schilling <coding@schilljs.com>
|
|
Signed-off-by: Joas Schilling <coding@schilljs.com>
|
|
Co-authored-by: Joas Schilling <coding@schilljs.com>
Signed-off-by: Vincent Petry <vincent@nextcloud.com>
|
|
Signed-off-by: Vincent Petry <vincent@nextcloud.com>
|
|
Fix number detection in participantType tests
The guests app is now enabled.
The spreed app is whitelisted for guest account users.
A password is now set for the guest account users to be able to log in properly.
Added system message tests for listable and read-only attributes.
Added tests scenarios for permission checks and room type checks before
setting listable attribute.
Added integration tests for /listed-rooms endpoint
Covers permissions to search and also with and without search terms.
Signed-off-by: Vincent Petry <vincent@nextcloud.com>
|
|
Signed-off-by: Vincent Petry <vincent@nextcloud.com>
|
|
Added a spreedcheats endpoint to allow creating guest account
users for integration tests.
Grabs the GuestManager from the guests app to create a guest user in the
correct backend.
Signed-off-by: Vincent Petry <vincent@nextcloud.com>
|
|
Added guest app to CI for callapi tests.
Added test scenarios for joining listable rooms.
Signed-off-by: Vincent Petry <vincent@nextcloud.com>
|
|
Bootstrap SystemMessage/ListenerTest.
Add test cases for user add event.
Signed-off-by: Vincent Petry <vincent@nextcloud.com>
|
|
Always join as USER when joining group or public room
Allow nulls for Oracle
Changes after review
Removed populateBaseRoomData and reused the existing code by adding an
extra condition for when querying listable rooms with null participant.
Co-authored-by: Joas Schilling <coding@schilljs.com>
Signed-off-by: Vincent Petry <vincent@nextcloud.com>
|
|
Signed-off-by: Vincent Petry <vincent@nextcloud.com>
|
|
Signed-off-by: Vincent Petry <vincent@nextcloud.com>
|
|
Added ability to set a conversation as listable for regular users and/or
guest users from the guest app.
This only implements the flag, endpoint and UI to manage it but not yet
making it appear in search results.
Signed-off-by: Vincent Petry <vincent@nextcloud.com>
|