You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 23, 2024. It is now read-only.
For massive multi-node support at the application level, we should allow a fallback option for email/ip verification for protected user actions like new posts.
Example: Sharing content from one Reverse instance to others on different domains that don't share db creds.
In those situations, without access to the Mongo session where the user logged in, the instance would fallback to Dereva's email/ip auth and send a verification before allowing the cross-domain action.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
For massive multi-node support at the application level, we should allow a fallback option for email/ip verification for protected user actions like new posts.
Example: Sharing content from one Reverse instance to others on different domains that don't share db creds.
In those situations, without access to the Mongo session where the user logged in, the instance would fallback to Dereva's email/ip auth and send a verification before allowing the cross-domain action.
The text was updated successfully, but these errors were encountered: