FAQ

L’Identité Numérique La Poste (LINLP) is a unique digital key accessible from your smartphone, allowing you to complete online procedures simply and securely.

It combines:

• certified identity verification performed beforehand
• a strong authentication solution
• controlled sharing of user data

👉 It allows users to securely prove their identity online.

FranceConnect+ is an identity federation allowing access to various compatible public and partner services.

LINLP is an identity provider that can be used:

• directly by partners through dedicated integration
• within the FranceConnect+ ecosystem

LINLP mainly relies on:

• OpenID Connect
• OAuth 2.0

The recommended standard flow is:

Authorization Code

👉 It provides the highest level of security for web and application integrations.

Yes.

The following journeys can be supported depending on the chosen architecture:

• web
• mobile web
• mobile application
• cross-device journeys

Depending on authorized scopes:

• pivot identity
• email
• phone number
• nationality
• documentary data
• account metadata

👉 See: Scopes and Claims

No.

The `preferred_username` field:

• is declarative
• freely entered by the user
• not verified by LINLP

👉 It must not be used as trusted reference data.

No.

Returned data depends on:

• requested scopes
• authorized configuration
• user consent
• data availability

Yes.

The `id_token` constitutes:

• proof of authentication
• a signed token
• an element that can be verified afterwards

👉 It is recommended to retain it according to the partner’s internal policies.

Yes, systematically:

• signature
• issuer
• audience
• expiration
• nonce (if used)

No.

⚠️ The `client_secret` is strictly confidential and must remain on the backend.

Yes:

• Sandbox
• dedicated test accounts

Submit a request to the LINLP team with:

• project context
• redirect_uri
• requested scopes
• designated owner

No.

Each environment has separate credentials:

• Sandbox
• Production

No.

It appears only:

• during the first authentication on the service
• when new scopes are requested
• with the `prompt=consent` parameter

Yes.

Authentication relies on mobile validation through the LINLP application.

The journey is interrupted and authentication does not succeed.