Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Captcha #89

Open
blackst0ne opened this issue Mar 14, 2018 · 0 comments
Open

Captcha #89

blackst0ne opened this issue Mar 14, 2018 · 0 comments
Labels
components enhancement Enhancement of existing features
Milestone

Comments

@blackst0ne
Copy link
Contributor

On the current version of eqalert.ru we have two pages with reCAPTCHA enabled:

  1. Authorization page: https://eqalert.ru/ru/users/sign_in
  2. Registration page: https://eqalert.ru/ru/users/sign_up

Since we now are migrating to the SPA architecture, the captcha feature must be implemented both on client (vuejs, this repository), and on API (seismo-api).

This is not very big challenge.

The most interesting thing here lays in the API layer: how to distinguish clients (require a reCAPTCHA token from web clients, do not require tokens from other clients).

@jamm1985 the main question of this issue is, do we want to add captcha functionality at all?

/cc @DoctorLines @bogdanevg

@blackst0ne blackst0ne added this to the Backlog milestone Mar 20, 2018
@blackst0ne blackst0ne added enhancement Enhancement of existing features components labels Mar 20, 2018
@jamm1985 jamm1985 modified the milestones: Backlog, v3.1.0 Dec 19, 2022
@jamm1985 jamm1985 modified the milestones: v3.1.0, Backlog Feb 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
components enhancement Enhancement of existing features
Projects
None yet
Development

No branches or pull requests

2 participants