Authentication on e-habillement relies on the MinDefConnect portal, which means that most blockages do not come from the platform itself but from the technical chain between the user workstation and the identity provider. Before seeking support from the Commissariat des armées, some methodical checks can resolve most situations.
Security certificates and system time: the invisible cause of MinDefConnect failures
A system clock discrepancy of just a few minutes is enough to invalidate the TLS negotiation with the authentication server. The browser then considers the certificate as expired or not yet valid and blocks the connection without displaying an explicit message related to the time.
Related reading : How to use a GPS without an internet connection with Mappy during your travels
We recommend first checking that automatic time synchronization is enabled on the workstation. In Windows, the setting can be found in Settings > Time & Language > Date & Time. The “Set time automatically” option must be set to “On,” and the time zone should match the actual location.
On a workstation configured on the Défense network, NTP synchronization may be managed by domain policy. If the discrepancy persists after manual activation, the problem lies with the local infrastructure, not e-habillement. When encountering a connection issue with e-habillement, this reflex about system time is often overlooked, even though it resolves a significant portion of cases.
Further reading : Kerterre: the main drawbacks to know before getting started
Cache, cookies, and MinDefConnect session: purge in the right place
Clearing the browser cache remains the most common advice, but it needs to be targeted correctly. A global purge also removes active sessions on other Défense applications, which creates unnecessary inconveniences.
The precise method is to delete only the cookies associated with the following domains:
- habillement.defense.gouv.fr: the main domain of the e-habillement platform, which stores the application session cookie
- The domain of the MinDefConnect portal used for SSO authentication, whose SAML cookie may remain stuck in an invalid state after a sudden disconnection
- Any third-party domain related to the ministry’s CDN, which may cache an outdated redirect
On Chrome, the procedure goes through Settings > Privacy and security > Cookies and other site data, then searching by domain name. Firefox offers similar access via the address bar by clicking on the padlock.
The private browsing test
Opening a private browsing window allows you to instantly bypass any cache or corrupted cookie issues. If the connection succeeds in private browsing, the diagnosis is made: the problem comes from a local state of the browser, not the server.
If the connection also fails in private browsing, the problem lies upstream (network, proxy, DNS). This test takes a few seconds and avoids pursuing unnecessary application diagnostics.
Firewall, proxy, and network restrictions on e-habillement
Connections from a corporate network, a barracks, or a military health facility often pass through a filtering proxy. Some proxies block requests to subdomains of the ministry or interrupt the ongoing SSO authentication flow.
The typical symptom: the MinDefConnect login page displays, the credentials are accepted, but the redirect to e-habillement loops or stops on a blank page. This behavior indicates an interruption of the SAML flow by an intermediate network device.
To isolate this cause, we recommend testing the connection from a different network:
- Sharing a connection from a personal phone on 4G or 5G, which completely bypasses the local proxy
- Home Wi-Fi network, which generally has no filtering on .gouv.fr domains
- Another workstation on the same network, to check if the blockage is specific to the machine or global
If the connection works on an alternative network, the problem is confirmed on the local infrastructure side. Resolution then goes through the RSSI or network administrator of the unit, not through e-habillement support.
Browser version and compatibility with Défense portals
The portals of the Ministry of the Armed Forces use recent security protocols. An outdated browser may not support the required TLS version and fail silently at the negotiation stage.
Chrome, Firefox, and Edge in their current versions are compatible. Internet Explorer, on the other hand, has not been supported by Microsoft for several years and regularly causes failures on the ministry’s SSO portals. Some active service workstations still retain IE as the default browser in their configuration.
To quickly check the version: menu “Help” then “About” in Chrome, Firefox, or Edge. If an update is available, the browser will offer it directly from this page.
Extensions that interfere with authentication
Ad blockers, enhanced security extensions, and certain VPNs built into the browser can intercept or modify authentication requests. Temporarily disabling all extensions before a connection test allows you to rule out this avenue in a few clicks.
Preparing an effective support ticket for e-habillement
If none of the previous checks resolve the blockage, contacting support becomes necessary. The quality of the information provided directly influences the processing time.
A well-written ticket contains the exact error message (copied-pasted or screenshot), the browser used with its version, the type of network (Intradef, civilian network, 4G), the precise time of the attempt, and the diagnostic steps already taken.
Explicitly mentioning that the private browsing test and the test on an alternative network have been performed allows support to move directly to the next level of diagnosis. Without this information, the first response will almost systematically be to request these same checks, which extends the resolution time by several days.
The contact page is accessible directly from habillement.defense.gouv.fr via the “Contact us” link at the top of the page, including without being authenticated. This point is useful when the blockage prevents any navigation on the platform.