User Journey

Describe the user journey during an authentication with L’Identité Numérique La Poste.

👉 This page helps understand the end-user experience.

The journey relies on an interaction between:

• the partner service
• LINLP
• the user’s smartphone

• The user accesses the partner service
• They choose “Sign in with L’Identité Numérique La Poste”

• The user is redirected to the LINLP identification screen
• They enter their phone number

• An authentication request is sent to their phone
• The LINLP application opens

• The user confirms their identity:
  • using their secret PIN code

👉 This step constitutes strong authentication (2FA)

⚠️ This step is optional.

It is displayed only in the following cases:

• first authentication of the user on the service
• changes to requested scopes
• consent is forced during the `/auth` call using `prompt=consent`

👉 The user then reviews the requested data and approves sharing.

💡 Outside these cases, this step is not displayed and the journey continues directly.

• The user is redirected back to the partner service
• Their information is shared with the service

👉 The partner service receives:

• proof of authentication (`id_token`)
• user data (depending on scopes)

• The user rejects the request
• Return to the authentication screen

• The user does not validate in time
• The request expires

• Phone number not associated with a LINLP identity
• Timeout followed by return to the authentication screen

⚠️ The journey depends on the smartphone

• The user must have access to their phone.

⚠️ Validation delay

• Provide a waiting state on the interface.

• The journey is simple and secure
• The user always validates on their smartphone
• The service never manages credentials
• Authentication relies on two factors (mobile device and secret code)

👉 See use cases:

Use Cases