All releases
ProductAvailable

Email verification and credential performance

The engine added an asynchronous verification redirect flow and tuned credential derivation and tenant-aware email handling.

Mohith / 3 min read

What changed

Registration now enters an email-verification flow before normal login. Delivery can happen asynchronously, and a valid verification link is processed by the engine before any project callback.

Credential derivation parameters and tenant-aware email handling were tuned without removing the requirement for password-strength and breach-response controls.

Completion boundary

A delivery acknowledgement is not proof that the address was verified. The engine changes verification state only after it validates the token, and an application callback receives a bounded result rather than the verification secret.

Asynchronous by design

Registration can return before email delivery completes. Applications should present a pending state and support an explicit resend path instead of treating delivery delay as registration failure.