Ping–Fluent Authentication Loop Prevention Update
Release
Author:
Yulia Andreyanova
Changed on:
16 Jan 2026
| Target release date: | 2026-01-12 |
|---|---|
| Release status: | Development |
Description
ONGOING DEPLOYMENTWe are currently updating the content on this page due to an ongoing deployment. Some information might be out of date. Please reach out if you have any concerns.This update significantly improves login reliability for users authenticating through Ping-based SSO.
Previously, users could encounter an infinite redirect loop between Ping and Fluent when their account lacked required permissions or configuration (e.g., missing primaryLocation). This prevented a successful login and provided no guidance to resolve the issue.With this enhancement, Fluent now detects failed login attempts caused by account configuration issues and displays a clear, user-friendly error message, rather than restarting the authentication flow.This prevents user lockout, reduces support escalations, and ensures more transparent and predictable authentication behavior across all Fluent modules.
Changelog
- Implemented logic to detect scenarios where Ping provides a valid JWT token but Fluent login fails due to missing permissions.
- Added support for displaying backend-provided error messages in the standard “Whoops” error view.
- Prevented re-triggering of Ping authentication when Fluent login fails for non-authentication reasons.
- Applied loop-prevention logic consistently across all Fluent applications using Ping-based authentication.
Screenshot
| Released capability depth: | Enhancement |
|---|---|
| Release bundle / Capability type: | Web apps, Platform |
