The Air France IPN is the intranet portal that group employees use daily to check their schedules, manage their administrative tasks, and access business tools. Behind this acronym lies a technical ecosystem that has significantly evolved since 2024, with the centralization of credentials and the strengthening of authentication. Understanding these changes helps avoid the most common blockages, often misdiagnosed by users.
Conflict between personal VPN and IPN connection: the most underestimated problem
The majority of reports of “blank page” or “inaccessible site” on Intralignes and IPN are not due to a server outage. Since 2024, field feedback shows that using a personal VPN blocks access to Air France’s internal portals when connecting remotely.
NordVPN, Surfshark, iCloud private relay, or a custom DNS conflict with Air France’s iPN VPN. The portal then does not return any explicit error message, leading many users to believe there is a general malfunction.
The documented operational recommendation is simple: disable any third-party VPN and any Apple private relay before launching the iPN VPN, and only then open Intralignes or IPN. This sequencing resolves the vast majority of blockages without needing to contact support.
For those wishing to access the Air France IPN platform from home, this prior check should become a systematic reflex, just like checking the password.
Active Directory password: a unique identifier, multiple locked portals
Since 2024, Air France has centralized access around a unique Active Directory password. The same identifier opens Intralignes, GPNet, and IPN. This simplification has a downside: when the AD password expires, all these portals become inaccessible simultaneously.
Many employees interpret this global lockout as a technical failure. In reality, simply renewing the Active Directory password restores access to all services. The identifier format follows a logic specific to each entity of the group:
- For Air France staff, the identifier takes the form of m followed by the first six digits of the employee number (example: m123456).
- For KLM staff, the format is k followed by six digits, with a historical variant including a zero after the k for older accounts.
- For external contractors, the identifier starts with t or x followed by the last six digits of the badge number.
An expired password does not always generate a clear message on the login page. If access is denied without explanation, checking the expiration date of the AD password remains the first diagnosis to make.
PingID authentication and connection security on Air France IPN
Two-factor authentication via PingID has become mandatory to connect to the group’s internal portals. This system adds a layer of verification after entering the password: the user receives a notification on the PingID app installed on their phone and must validate it to complete the connection.
PingID blocks access if the app is not properly paired with the employee’s account. Several situations can cause this type of blockage:
- Changing phones without transferring the PingID profile beforehand, which requires going through a re-registration process.
- Updating the mobile operating system that resets notification permissions, preventing the validation request from being received.
- Using an unstable mobile network at the time of the connection attempt, which causes the PingID response time to expire.
In case of persistent blockage related to PingID, the procedure is to contact ICT support. The available data does not indicate whether Air France plans to integrate other authentication methods (passkey, native biometrics) in the short term.
IPN, Intralignes, and GPNet: three portals, three distinct scopes
The confusion between these three tools is common, even among employees who have been in position for several years. Each covers a different functional scope, even though the entry point often goes through Intralignes.
Intralignes (accessible via intralignes.airfrance.fr) serves as the central authentication portal. It is the gateway to other services. IPN brings together business tools, schedules, and HR documents intended for flight crew and ground staff. GPNet, on the other hand, is dedicated to managing discounted tickets reserved for employees and their dependents.
An employee looking for their flight schedule does not need GPNet. Another who wants to book a ticket for a relative will not find this feature on IPN. Identifying the correct portal before logging in avoids navigation errors that waste time.
Remote access and network constraints on the IPN platform
Connecting from outside the corporate network imposes specific constraints. Air France’s iPN VPN must be activated before any attempt to connect to Intralignes or IPN. This VPN creates a secure tunnel between the user’s workstation and the group’s internal network.
Recent web browsers (Chrome, Firefox, Safari) are compatible with the platform, but some browser extensions interfere with the authentication process. Ad blockers and privacy extensions can prevent the PingID login page from loading correctly.
Disabling browser extensions during login is a second reflex to adopt, after disabling the personal VPN. These two precautions combined cover almost all reported blockage cases by remote users.
Access to IPN remains conditional on the active employee status of the Air France-KLM group. A suspended account (departure, unconfigured long-term leave) requires manager intervention for reactivation. Technical support cannot process this request without prior hierarchical approval.