Running Front End with OIDC Disabled Issue

[AlaeMghirbi]

Description

When running the Tmail frontend without Single Sign-On (SSO), using a local backend and basic login, the application still performs an OIDC discovery request at startup.
This prevents the basic login form from appearing and makes it impossible to use Tmail without SSO.

Expected result

• The application should start and display the basic login form when SSO is not configured.

Current behavior

• On startup, the frontend automatically calls _checkOIDCIsAvailable() in LoginController.

• This method triggers an OIDC discovery request to:
  http://localhost:8001/.well-known/openid-configuration

• Since the backend does not expose OIDC endpoints, the request returns 404, causing:

• A ClientException: NetworkError

• A retry loop in _checkOIDCIsAvailable()

• The login form never appearing

Preconditions

.env configuration:

SERVER_URL=http://localhost:8001

Backend

• Running locally with No OIDC configuration enabled

Reproduction Steps

1. Start the backend locally on port 8001 without OIDC.
2. Run the frontend locally
3. Open the browser console.
4. Observe

• Request to /.well-known/openid-configuration
• Network error logs
• Login form not displayed

Acceptance criteria

• The frontend must provide a way to disable OIDC, for example via a .env variable:

  USE_OIDC=false ```
  

1. When USE_OIDC=false:

• _checkOIDCIsAvailable() should not be called.

• The basic login form should be displayed immediately and no OIDC discovery or OpenID requests should be made.

2. When USE_OIDC=true:

The current SSO (OIDC) flow must continue to function normally.

Additional information

Issue occurs consistently (100% reproducible)

** logs: **

further problem analysis : https://amghirbi-notes.twake.linagora.com/public/?sharecode=Epw76v88J5aj

[chibenwa]

How about having _checkOIDCIsAvailable return false when the request ends up in 404 ?

Cc @hoangdat