Outils pour utilisateurs

🇫🇷 Français | 🇬🇧 English


Endpoints

Objective

Present the main endpoints available to integrate L’Identité Numérique La Poste through OpenID Connect.

👉 This page centralizes useful URLs for Sandbox and Production environments.


Base URLs

OpenID Connect Endpoints

Authorization Endpoint

Used to initiate user authentication.

GET /auth/realms/partenaire/protocol/openid-connect/auth

👉 Used in the Authorization Code flow.


Token Endpoint

Used to exchange a code for tokens.

POST /auth/realms/partenaire/protocol/openid-connect/token

👉 Returns:

  • access_token
  • id_token
  • expires_in

UserInfo Endpoint

Used to retrieve user data.

GET /auth/realms/partenaire/protocol/openid-connect/userinfo

👉 Requires a valid access_token.


Certificates / Public Keys

Used to verify JWT signatures.

GET /auth/realms/partenaire/protocol/openid-connect/certs

👉 Returned in JWKS format.


OpenID Connect Configuration

Standard document containing the full configuration.

GET /auth/realms/partenaire/.well-known/openid-configuration

👉 Recommended for automated integration.


Sandbox Example

https://authent.pprod.lidentitenumerique.laposte.fr/auth/realms/partenaire/.well-known/openid-configuration

Best Practices

⚠️ Use `.well-known/openid-configuration` To automatically retrieve endpoints.

⚠️ Do not hardcode public keys Use the `/certs` endpoint.

⚠️ Verify environments Sandbox and Production use different URLs.


Points of Attention

⚠️ Always use HTTPS.

⚠️ `/token` calls must be performed server-side only.


Key Takeaways

  • All LINLP endpoints rely on OpenID Connect
  • `.well-known` is the main reference
  • `/certs` allows JWT verification

Next Step

👉 Understand environments:

Environments

This website uses cookies. By using the website, you agree with storing cookies on your computer. Also, you acknowledge that you have read and understand our Privacy Policy. If you do not agree, please leave the website.

Plus d’informations