mirror of https://github.com/zulip/zulip.git
423aebf98e
The way the flow goes now is this:
1. The user initiaties login via "Billing" in the gear menu.
2. That takes them to `/self-hosted-billing/` (possibly with a
`next_page` param if we use that for some gear menu options).
3. The server queries the bouncer to give the user a link with a signed
access token.
4. The user is redirected to that link (on `selfhosting.zulipchat.com`).
Now we have two cases, either the user is logging in for the first time
and already did in the past.
If this is the first time, we have:
5. The user is asked to fill in their email in a form that's shown,
pre-filled with the value provided inside the signed access token.
They POST this to the next endpoint.
6. The next endpoint sends a confirmation email to that address and asks
the user to go check their email.
7. The user clicks the link in their email is taken to the
from_confirmation endpoint.
8. Their initial RemoteBillingUser is created, a new signed link like in
(3) is generated and they're transparently taken back to (4),
where now that they have a RemoteBillingUser, they're handled
just like a user who already logged in before:
If the user already logged in before, they go straight here:
9. "Confirm login" page - they're shown their information (email and
full_name), can update
their full name in the form if they want. They also accept ToS here
if necessary. They POST this form back to
the endpoint and finally have a logged in session.
10. They're redirected to billing (or `next_page`) now that they have
access.
|
||
|---|---|---|
| .. | ||
| ci | ||
| documentation_crawler | ||
| droplets | ||
| i18n | ||
| lib | ||
| linter_lib | ||
| node_lib | ||
| oneclickapps | ||
| setup | ||
| test-install | ||
| tests | ||
| zulip-export | ||
| README.md | ||
| __init__.py | ||
| build-docs | ||
| build-release-tarball | ||
| cache-zulip-git-version | ||
| check-capitalization | ||
| check-frontend-i18n | ||
| check-issue-labels | ||
| check-openapi | ||
| check-provision | ||
| check-schemas | ||
| check-templates | ||
| check-thirdparty | ||
| clean-branches | ||
| commit-message-lint | ||
| commit-msg | ||
| conf.ini-template | ||
| coveragerc | ||
| deploy-branch | ||
| diagnose | ||
| documentation.vnufilter | ||
| duplicate_commits.json | ||
| fetch-contributor-data | ||
| fetch-pull-request | ||
| fetch-rebase-pull-request | ||
| find-unused-css | ||
| generate-integration-docs-screenshot | ||
| lint | ||
| message-screenshot.js | ||
| pre-commit | ||
| provision | ||
| push-to-pull-request | ||
| rebuild-dev-database | ||
| rebuild-test-database | ||
| release | ||
| release-tarball-exclude.txt | ||
| renumber-migrations | ||
| reset-to-pull-request | ||
| review | ||
| run-codespell | ||
| run-dev | ||
| run-mypy | ||
| run-tsc | ||
| semgrep-py.yml | ||
| setup-git-repo | ||
| show-profile-results | ||
| stop-run-dev | ||
| tail-ses | ||
| test-all | ||
| test-api | ||
| test-backend | ||
| test-documentation | ||
| test-help-documentation | ||
| test-js-with-node | ||
| test-js-with-puppeteer | ||
| test-locked-requirements | ||
| test-migrations | ||
| test-queue-worker-reload | ||
| test-run-dev | ||
| test-tools | ||
| total-contributions | ||
| update-locked-requirements | ||
| update-prod-static | ||
| update-zuliprc-api-field | ||
| upload-release | ||
| webpack | ||
| zanitizer | ||
| zanitizer_config.pm.sample | ||
README.md
This directory contains scripts that are used in building, managing,
testing, and other forms of work in a Zulip development environment.
Note that tools that are also useful in production belong in
scripts/ or should be Django management commands.
For more details, see https://zulip.readthedocs.io/en/latest/overview/directory-structure.html.