Development on NolarFlow is progressing ΰ€€ΰ₯ΰ€ΰ₯, and weβre ahead of schedule on multiple parts of the system.
Because of this progress, we now expect that the planned maintenance to migrate our authentication systems may be moved forward from May 29 to April 30 or earlier.
This is still an estimate and may change, but things are moving fast in the right direction.
Current Progress
Weβre not only building what was planned β weβre going beyond it.
Several new features are already being implemented as part of NolarFlow:
Advanced control over 2FA bypass per passkey
Ability to configure 2FA behavior per SSO provider
More granular trust-based authentication logic
Smarter 2FA Control
One of the bigger improvements is how flexible 2FA becomes:
Each passkey can be configured to allow or deny 2FA bypass
Each SSO provider (Google, Discord, GitHub, Twitch) can have its own 2FA rules
By default, 2FA bypass is disabled for all SSO providers
If 2FA is enabled on your account, you will always see the 2FA step unless you explicitly allow bypass
This means you can treat trusted and untrusted access differently.
For example, you could allow bypass on a trusted device or provider, while keeping stricter checks elsewhere.
All of these settings can be changed at any time.
Whatβs Next
Weβre continuing to expand NolarFlow with more features and improvements beyond the original scope. The goal is to deliver a flexible, secure, and developer-friendly authentication system that works seamlessly across all platforms.
More updates will follow as we get closer to rollout.
β Software By Ricardo