The Air France IPN is the intranet portal that group employees use daily to check their schedules, manage their HR processes, and access memos. Its setup generally does not pose technical difficulties, but several intermediate steps, from the VPN to two-factor authentication, create recurring blocks, particularly for new hires or staff connecting from personal devices.
Technical chain to connect to the IPN from a personal device
Accessing the IPN from a personal device is not limited to entering a username and password. As soon as the connection is made outside the Air France internal network, several layers of security are added.
To reach the IPN or Intralignes from a personal computer, three layers of security must be crossed in a specific order: active iPN VPN, Habile/Active Directory authentication, and then PingID validation. Skipping a step or reversing the order results in a connection refusal without an explicit error message.
Employees wishing to access the Air France IPN from home must also consider often-overlooked network settings. Recent technical sources indicate that certain common settings on personal machines block the connection:
- The iCloud private relay (enabled by default on recent Macs) interferes with the iPN VPN tunnel and prevents the resolution of internal Air France addresses.
- Personal VPNs (NordVPN, ExpressVPN, etc.) conflict with the iPN VPN. Only one VPN can be active at a time, and it must be Air France’s.
- Secure DNS (DoH), offered by Chrome and Firefox, redirects DNS queries outside the VPN tunnel, making the intranet inaccessible even with an established VPN connection.
Disabling these three elements before launching the iPN VPN resolves the majority of support tickets related to remote access.
Unification of credentials: what has changed for IPN, Intralignes, and GPNet
Until recently, employees had to juggle multiple username/password pairs depending on whether they accessed IPN, Intralignes, or GPNet. This situation generated ongoing confusion, particularly after a password renewal on just one of the tools.
Recent technical documentation indicates that the GPNet password now corresponds to the Windows/Active Directory password. In practice, the same password is used for the Windows session at the office, for the IPN, and for GPNet. Changing the Windows password updates it across all these services.
The username remains the employee number in a six-digit format, sometimes preceded by the letter “m”. This unification simplifies daily management but creates a side effect: an expired or blocked password on Active Directory simultaneously locks all accesses. In case of a blockage, the reset must go through internal IT support, not through a public online form.
PingID as a mandatory second factor
Two-factor authentication via PingID has become mandatory. The app, installed on the employee’s personal or work phone, generates a push notification for each login attempt. Without PingID validation, access is denied even if the username and password are correct.
PingID can pose difficulties in areas with weak network coverage. Some flight personnel report notification failures while on layover, forcing them to use the temporary code generated offline by the app. This feature exists but remains poorly documented in internal resources.
Activation delay for new hires’ IPN accounts
A point rarely addressed in official guides concerns the actual delay between signing the contract and gaining effective access to the IPN. Activation depends on administrative processing by human resources, and several recent reports indicate a delay ranging from a few days to two weeks.
For short-term contracts, this delay poses a concrete problem: an employee hired for a limited period may lose a significant part of their contract without access to their digital work tools. Available data does not determine whether Air France has implemented an expedited procedure for these profiles.
While waiting for activation, newcomers generally rely on a colleague or supervisor to check schedules and instructions. This informal situation is not documented in any official process, but it remains common in testimonies from recently integrated staff.
IPN, Intralignes, and GPNet: distinct scopes not to be confused
The confusion between these three tools arises regularly. Each covers a different functional scope, even though the unification of credentials gives the impression of a single tool.
- IPN centralizes HR information, memos, and administrative documents related to the employee’s career.
- Intralignes is the ticketing platform with preferential rates reserved for employees of the Air France-KLM group and their dependents.
- GPNet manages flight schedules and operational data for flight personnel. It is little used by ground staff.
Attempting to check flight schedules via IPN or to book a ticket via GPNet leads to a dead end. Each tool has its own entry URL, even though the authentication layer is shared.
Should you keep Intralignes open permanently on your device?
Some employees leave an Intralignes or IPN tab open all day to avoid having to reconnect. This habit can cause silent session disconnections, where the page appears active but no longer refreshes the data. Closing and reopening the session remains more reliable than simply refreshing the page, especially after a prolonged sleep of the device.
The internal technical support number (+33 (0) 2.46.84.13.24) remains the primary recourse in case of persistent blockage. Internal forums and union groups also relay occasional solutions, but their reliability varies according to updates to the group’s IT infrastructure.