The Russian identity protection developer Indeed has updated its Indeed MFA service. The new version introduces a fallback authentication method that allows users to enter a one-time code manually if a push notification via the Indeed Key app fails to arrive or is not confirmed in time.
This fallback feature is available for integrations using Indeed agents. For RADIUS-based scenarios, the client application must support the Challenge-Response technology to facilitate the sequential exchange of authentication requests and responses.
The update also enhances pre-authentication rules by allowing them to be based on Keycloak GUIDs. This improvement enables the construction of nFactor chains, providing organizations with more granular control over authentication workflows based on specific user requirements and infrastructure systems.
Administrative capabilities have been expanded to include customizable system notification recipients and alerts regarding the expiration of push-proxy access certificates. Administrators can now also define a grace period for users with non-activated tokens to operate without a second factor.
Additionally, the developer has refined the billing logic for accounts transitioning from test mode to production. According to Galust Shakhbazyan, Commercial Director of Indeed Cloud, these updates aim to increase the flexibility and resilience of authentication scenarios for corporate clients.
