Aman-Mittal opened a new issue, #749: URL: https://github.com/apache/fineract-backoffice-ui/issues/749
## What happens Two settings screens load an editable empty form even though their first request failed, and they say nothing about it. | Screen | Request | Response | What the user sees | |---|---|---|---| | Settings → Two-Factor Authentication Config (`/settings/two-factor`) | `GET /twofactor/configure` | **404** | An empty "Configuration (JSON)" editor and an enabled **Save Config** button | | System → OIDC Configuration (`/system/oidc-config`) | `GET /tenants/default/oidc-config` | **404** | Empty Issuer / Client ID / Scopes fields with enabled **Delete** and **Save** | The 404s are expected on a backend where those features aren't enabled (two-factor is off by default in Fineract, and the sandbox has no OIDC config). That part is environmental, not a UI defect. The UI defect is that both screens treat the 404 as an empty, editable configuration: - An administrator can't tell "this feature is disabled on the server" apart from "this feature is enabled and has no settings yet". - **Delete** is offered for an OIDC config that doesn't exist. - Saving the two-factor JSON against a server where the module is off can only fail, and nothing on the screen warns about that beforehand. ## Suggested fix Handle the load failure explicitly on both screens: - **404 on two-factor:** show "Two-factor authentication is not enabled on this Fineract server" and disable editing. - **404 on OIDC:** show "No OIDC configuration for this tenant" with a Create action, and hide Delete until a config exists. - Any other error: the standard error state, not a blank form. ## Tested against Deployed build of `main` (https://aman-mittal.github.io/fineract-backoffice-ui), backend `sandbox.mifos.community`, Chrome 1440×900, 2026-10-16. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
