-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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の設定に不備があるとログインが行えなくなる #15137
Labels
[Feat] ControlPanel
Issues related to existing functionality, such as bugs or adding small features.
🔥high priority
Comments
samunohito
added
the
[Feat] ControlPanel
Issues related to existing functionality, such as bugs or adding small features.
label
Dec 18, 2024
Captchaの設定を保存するためにCaptchaを解かせるとか |
管理画面の設定項目付近に動作確認用のCaptchaがあるのは良いかも |
それはあったはず |
(しらなかった) |
使えることを強制的に確認させる+(サーバーサイド処理含め)Captchaを解く一連の流れをテストさせる目的で設定したCaptchaを自分で解いてみないと保存できないようにすると確実そうかなと |
誰か余力のある人いますか |
やるかあ |
This comment has been minimized.
This comment has been minimized.
5 tasks
sequenceDiagram
actor user as User
participant client as frontend
participant server as backend
participant db as database
participant captcha as CAPTCHA Provider
user ->>+ client: Botプロテクション設定変更の表示
client ->>- user: _
user ->>+ client: 設定変更内容の入力
client ->>+ captcha: CAPTCHAウィジェットの取得
captcha ->>- client: CAPTCHAウィジェットの返却
client ->>- user: _
user ->>+ client: CAPTCHA入力
client ->>+ captcha: CAPTCHA入力検証
captcha ->>- client: 応答トークン
client ->>+ server: 設定変更内容+応答トークンの送信
server ->>+ captcha: 応答トークン検証
captcha ->>- server: 検証結果
note over server: 検証がOKじゃないとDBに保存しない=有効化出来ない
opt 検証結果 == OK
server ->>+ db: 設定変更内容の保存
db ->>- server: _
end
server ->>- client: _
client ->>- user: _
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
[Feat] ControlPanel
Issues related to existing functionality, such as bugs or adding small features.
🔥high priority
💡 Summary
CAPTHCAの設定に不備があることに気付けない
🥰 Expected Behavior
エラーがコントロールパネルもしくはログイン画面に出る
🤬 Actual Behavior
出ない
📝 Steps to Reproduce
No response
💻 Frontend Environment
🛰 Backend Environment (for server admin)
Do you want to address this bug yourself?
The text was updated successfully, but these errors were encountered: