France Connect Py
france-connect-py is a package allowing to interact with FranceConnect V2
through a single and easy-to-use class.
Requirements
france-connect-py only support the supported version of each dependency (mainstream & lts).
Python(supported versions)
Installation
The easiest way to install france-connect-py is through pip:
pip install france-connect-py
How to use
You only need to import the FranceConnect class and create an instance to
start using the France Connect API.
from france_connect.clients import FranceConnect
from france_connect.scopes import ACRValues, Scopes
fc = FranceConnect(
client_id="<client_id>",
client_secret="<client_secret>",
scopes=[Scopes.PROFILE, Scopes.IDENTITE_PIVOT],
# Must be THE SAME url as defined in FranceConnect
# No additional query params
# Do not forget the potential trailing slash
login_callback_url="<login_callback_url>",
logout_callback_url="<logout_callback_url>",
fc_base_url="https://fcp-low.integ01.dev-franceconnect.fr",
)
# You can retrieve the FranceConnect's OpenID configuration as follow.
fc.get_configuration()
# Get the authorization URL.
#
# You can provide a specific `nonce` and `state` if needed, or let the class
# generate them as a random 64 bytes hex string. You can also inherit
# `FranceConnect` and override `generate_nonce()` and `generate_state()` to change
# the way they are generated.
#
# `eidas1` is used as the default level of end user assurance, you can provide
# a different value using the `acr_values` parameter.
# For more information, see:
# https://docs.partenaires.franceconnect.gouv.fr/fs/fs-technique/fs-technique-eidas-acr/
#
# The `login_callback_url` provided at instantiation will be used as the
# callback URL, you can override it using the `callback_url` parameter.
url, nonce, state = fc.get_authentication_url(acr_values=[ACRValues.EIDAS2])
# The following code must be called when the user is redirected back to the
# service provider after a successful authentication of FranceConnect.
#
# Retrieve the code from the FranceConnect request
code = ...
# Retrieve the ID Token (the signature is verified automatically)
raw_token, decoded_token = fc.get_id_token(code)
# Retrieve the user's information using the ID Token (the signature is also
# verified automatically) `user_info` is a dictionary containing the user's
# information asked in the scopes.
user_info = fc.get_user_info(raw_token["access_token"])
# To retrieve the logout url, uses `get_logout_url()`.
#
# The `logout_callback_url` provided at instantiation will be used as the
# callback URL, you can override it using the `callback_url` parameter.
logout_url = fc.get_logout_url(raw_token["id_token"], state)
Other
france-connect-py uses the requests library to interact with the France
Connect API. You can override how the library is used using the following
FranceConnect class parameters:
timeout: int = 10verify_ssl: bool = Trueallow_redirects: bool = True
Changelog
2.1.1 (2025-09-22)
- Add conditional SSL handling in
verify_jwtwhen SSL verification is disabled. (#9),
2.1.0 (2025-05-20)
- Allow customization of JWT algorithms using
jwt_algorithmswhen instantiating client (#7), Contributed by Vayel.
2.0.0 (2024-10-07)
- Initial release
Metadata
Release files for france-connect-py 2.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| france_connect_py-2.1.1.tar.gz | 10.5 kB | Details |
Release files / france_connect_py-2.1.1.tar.gz
| Download URL | france_connect_py-2.1.1.tar.gz |
|---|---|
| Size | 10.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
032b32c02bd8682e18ae52cdcccde56d192fcb2d44000559e90170c2ea2dc2ee
|
|
BLAKE2b-256 checksum How to use checksums |
9ba9ec802bf5c4abc767cb97f6c6b0f9a3aad8be539660b90316289673009e32
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 22, 2025.
Transparency log