mirror of https://github.com/zulip/zulip.git
67ba20da81
If the server controls the registration's hostname, it can reclaim its registration credentials. This is useful, because self-hosted admins frequently lose the credentials when moving their Zulip server to a different machine / deployment method. The flow is the following: 1. The host sends a POST request to /register specifying registration_takeover=true. 2. The bouncer responds with a signed token. 3. The host prepares to serve this token at /zulip-services/verify and sends a POST to /remotes/server/register/verify_challenge endpoint of the bouncer. 4. Upon receiving the POST request, the bouncer GETS https://{hostname}/zulip-services/verify, verifies the secret and responds to the original POST with the registration credentials. 5. The host can now save these credentials to it zulip-secrets.conf file and thus regains its push notifications registration. |
||
---|---|---|
.. | ||
lib | ||
management | ||
migrations | ||
README.md | ||
__init__.py | ||
auth.py | ||
models.py | ||
urls.py | ||
views.py |
README.md
ZILENCER -- The Zulip license manager
This app is the place for storing state about various deployments of Zulip that exist in the world.