[PR #668] [MERGED] Support the native RPC-JSON protocol of the signal-cli package #678

New issue

Closed

opened 2026-02-26 06:31:49 +03:00 by kerem · 0 comments

kerem commented

2026-02-26 06:31:49 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/nextcloud/twofactor_gateway/pull/668
Author: @rotdrop
Created: 9/23/2025
Status: ✅ Merged
Merged: 9/23/2025
Merged by: @vitormattos

Base: master ← Head: feature/signal-cli

📝 Commits (2)

f692c78 Signal: make it work with native JSON-RPC endpoints of the signal cli package.
d510067 Polish the signal section of the documentation.

📊 Changes

2 files changed (+127 additions, -30 deletions)

View changed files

📝 doc/Admin Documentation.md (+15 -3)
📝 lib/Provider/Channel/Signal/Gateway.php (+112 -27)

📄 Description

The currently used protocols are partly outdated and refer to

https://gitlab.com/morph027/signal-cli-dbus-rest-api
https://gitlab.com/morph027/python-signal-cli-rest-api

which are considered obsolete by its author in favour of the the JSON-RPC interface of the signal-cli package.

There is also another Docker project

https://github.com/bbernhard/signal-cli-rest-api

which seemingly uses the API used by the obsolete "morph027" packages. However, as signal-cli already supports a remote API: why not use it, instead of having to install yet another package?

The old APIs including bbernhard are still supported though, just that the Signal-gateway first tries the native remote protocol of signal-cli and if that does not work out it falls back to what it did without this commit.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/nextcloud/twofactor_gateway/pull/668 **Author:** [@rotdrop](https://github.com/rotdrop) **Created:** 9/23/2025 **Status:** ✅ Merged **Merged:** 9/23/2025 **Merged by:** [@vitormattos](https://github.com/vitormattos) **Base:** `master` ← **Head:** `feature/signal-cli` --- ### 📝 Commits (2) - [`f692c78`](https://github.com/nextcloud/twofactor_gateway/commit/f692c7805a8b6d7cf1ac41870774c670c5449daf) Signal: make it work with native JSON-RPC endpoints of the signal cli package. - [`d510067`](https://github.com/nextcloud/twofactor_gateway/commit/d51006725943baeb971bd4e4ca077daa9611c64d) Polish the signal section of the documentation. ### 📊 Changes **2 files changed** (+127 additions, -30 deletions) <details> <summary>View changed files</summary> 📝 `doc/Admin Documentation.md` (+15 -3) 📝 `lib/Provider/Channel/Signal/Gateway.php` (+112 -27) </details> ### 📄 Description The currently used protocols are partly outdated and refer to https://gitlab.com/morph027/signal-cli-dbus-rest-api https://gitlab.com/morph027/python-signal-cli-rest-api which are considered obsolete by its author in favour of the the JSON-RPC interface of the signal-cli package. There is also another Docker project https://github.com/bbernhard/signal-cli-rest-api which seemingly uses the API used by the obsolete "morph027" packages. However, as signal-cli already supports a remote API: why not use it, instead of having to install yet another package? The old APIs including bbernhard are still supported though, just that the Signal-gateway first tries the native remote protocol of signal-cli and if that does not work out it falls back to what it did without this commit. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

kerem

2026-02-26 06:31:49 +03:00

closed this issue
added the
pull-request
label

kerem referenced this issue

2026-02-26 06:31:50 +03:00

[PR #678] [MERGED] chore(deps): Bump vue from 3.5.21 to 3.5.22 #687

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/twofactor_gateway-nextcloud#678

No description provided.

Rows
Columns