Welcome to the #dominoforever Product Ideas Forum! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated by HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.
For more information and upcoming events around #dominoforever, please visit our Destination Domino Page
With Domino now being an OIDC provider and fully capable IDP we are not planning to implement this feature request.
If you think it's still needed, please keep voting for it and comment here.
This is not a small amount of work to get this functional which is why we have concentrated on the Domino OIDC route as it benefits all customers, including our Nomad customers without SafeLinx.
MFA has become a hard requirement for any new externally facing service introduced into corporate networks, thanks to ISO27001 and similar security-focused certifications.
The backend (HCL Domino) already supports TOTP for a while already (Domino 12), SafeLinx-backed Nomad Web already exposes the GUI elements necessary, so it seems like it shouldn't be too much development effort to combine the two and expose TOTP through Nomad on Domino, without the significant overhead of either SafeLinx or a separate MFA-enabled IdP and SAML.
We are looking forward to implementing Nomad for Domino with Federated Login in our production environment, but without SafeLinx, which unfortunately is not possible yet.
Nomad Web for Domino should leverage Domino's built-in security architecture.
Removing Safelinx removes a significant barrier to using Nomad but the lack of ToTP will become just as big an issue.