-
Notifications
You must be signed in to change notification settings - Fork 32
♻️ webserver: Refactor login domain for CSR compliance and future confirmation logic #7417
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
♻️ webserver: Refactor login domain for CSR compliance and future confirmation logic #7417
Conversation
dda5c04 to
03c8cfc
Compare
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #7417 +/- ##
==========================================
+ Coverage 87.37% 87.45% +0.07%
==========================================
Files 1715 1717 +2
Lines 66613 66606 -7
Branches 1132 1132
==========================================
+ Hits 58205 58251 +46
+ Misses 8087 8034 -53
Partials 321 321
Continue to review full report in Codecov by Sentry.
🚀 New features to boost your workflow:
|
d82ee28 to
c1acfa7
Compare
GitHK
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks a lot!
dbe17d7 to
54904a5
Compare
sanderegg
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks
services/web/server/src/simcore_service_webserver/login/_controller/rest/twofa.py
Show resolved
Hide resolved
|



What do these changes do?
Refactored the old
logindomain to align with CSR layer requirements and in preparation for extending confirmation logic for sharing operations (ITISFoundation/private-issues#40).Confirmation Logic Overview
The confirmation logic is a mechanism for securely executing deferred actions via confirmation tokens. Each token, stored in the database, includes a secret code (
code), an associated function (action), and relevant parameters (data).When a user accesses a link containing the secret code, a designated GET entrypoint validates the token and triggers the corresponding action, using both the stored parameters and any additional context provided at runtime. Once executed, the confirmation entry is deleted.
This mechanism will be used to confirm sharing operations between users. For example, User A shares a project with User B and sends a confirmation link. When User B clicks the link, the system validates and executes the action, completing the sharing confirmation process.
Changes
Related issue/s
share_projectoperation (dev) and updates notifications-library #7431How to test
Dev-ops
None